This test failed again on stable-17.10.x, which carries the fix (Fix Version 17.10.14, commit 1aff52a4ed1): build #582.
This time the failure is in the new wait itself:
org.openqa.selenium.StaleElementReferenceException: The element with the reference ... is stale; either its node document is not the active document, or it is no longer connected to the DOM
at org.xwiki.test.ui.XWikiWebDriver.scrollTo(XWikiWebDriver.java:678)
at org.xwiki.test.ui.XWikiWebDriver.findElement(XWikiWebDriver.java:716)
at org.xwiki.test.ui.XWikiWebDriver.hasElementWithoutWaiting(XWikiWebDriver.java:162)
at org.xwiki.extension.test.po.ExtensionAdministrationPage.lambda$waitUntilIndexIsDone$0(ExtensionAdministrationPage.java:138)
at org.xwiki.test.security.ExtensionSecurityTest.checkForExtensionSecurityScanResult(ExtensionSecurityTest.java:61)
hasElementWithoutWaiting(".job-status .ui-progress") finds the progress bar and then scrolls to it, and the bar is removed when the job result replaces it, so the condition throws instead of returning false. The condition probably needs to tolerate a stale element.
The issue is left closed since its Fix Version is released; reopening it or filing a new one is a human decision.
Posted by the XWiki daily CI check (automated); ignore it if the analysis is wrong.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.