VersionIT#versionNavigation is flickering

The functional test org.xwiki.flamingo.test.docker.AllIT$NestedVersionIT#versionNavigation fails intermittently on the CI, on stable-17.10.x and stable-18.4.x (and once on master).

The test navigates between versions in the changes view, and the page object fails to find the "from" version link (#changes-info-box-from .changes-version link, excluding the arrow):

org.openqa.selenium.NoSuchElementException: Timed out after 10 seconds. Unable to locate the element
        at org.xwiki.flamingo.test.docker.VersionIT.versionNavigation(VersionIT.java:1086)

It is not random: it concentrates on PostgreSQL

Over the last 28 days, Develocity records 5 failures in 485 executions (1.0%), in two failure groups. The main one (4 of the 5) happens only with database = postgresql latest (16% of runs, p=0.0006):

• stable-17.10.x / chrome / postgresql latest / tomcat 11-jdk25 — 2/17 (11.8%)
• stable-18.4.x / chrome / postgresql latest / tomcat 11-jdk25 — 2/21 (9.5%)
• master / chrome / mysql latest / tomcat 11-jdk25 — 1/24 (4.2%), same selector, at VersionIT.java:1084

The other 22 configurations it runs in have never failed. First seen 2026-09-16, last seen 2026-09-30.

Evidence

• Build scans: https://community.develocity.cloud/s/vyabtruinvmkk , https://community.develocity.cloud/s/ddcsbzesmb3vc , https://community.develocity.cloud/s/x7mdzplrfkmoy , https://community.develocity.cloud/s/4a3a2gbhq6fbw
• CI build: https://ci.xwiki.org/job/XWiki%20Environment%20Tests/job/xwiki-platform/job/stable-17.10.x/306

Affected tests

• org.xwiki.flamingo.test.docker.AllIT$NestedVersionIT#versionNavigation

Affected branches: stable-17.10.x, stable-18.4.x, master.

Verifying a fix

At the 8.1% failure rate seen in the affected configurations, about 36 consecutive clean runs there are needed to conclude the failure stopped. They must be on chrome / postgresql latest / tomcat 11-jdk25, not on the default configuration, where this test has never failed.

Filed automatically by the daily CI check. If this is wrong or already covered by another issue, just close it.