You can see a video of the test failure here: https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php83-selenium/5343/artifact/log/Special%253AGlobalWatchlist-works-with-normal-display-2025-12-19T09-30-39-985Z.mp4 It's not exactly clear what is happening, but I assume there might be an error in the console, or the API response is really taking too long. The best way to investigate this is to check if it behaves the same way in a local installation...
Dec 19, 2025 15:29:37 G Rundlett <[email protected]>: > On Fri, Dec 19, 2025 at 5:06 AM יגאל חיטרון <[email protected]> > wrote: >> Well, I've tried. Fixed some problems, but one check fail on something weird. >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] Running: chrome >> (v120.0.6099.224) on linux >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] Session ID: >> 61d1baf9420e4a5556fc9608d3ca3da2 >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] » >> tests/selenium/specs/SpecialGlobalWatchlist.js >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] Special:GlobalWatchlist >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] ✖ works with normal display >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] 1 failing (18.4s) >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] 1) Special:GlobalWatchlist >> works with normal display >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] element >> (".ext-globalwatchlist-site") still not existing after 10000ms >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] Error: element >> (".ext-globalwatchlist-site") still not existing after 10000ms >> *11:30:51* [chrome 120.0.6099.224 linux #0-0] at async >> Context.<anonymous> >> (file:///workspace/src/extensions/GlobalWatchlist/tests/selenium/specs/SpecialGlobalWatchlist.js:44:3) >> (https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php83-selenium/5343/console) >> I do not know what to do with it. Can the code you suggested take so much >> time, or maybe it's something different? Maybe some part of the code can't >> get an answer because it isn't "a real wiki"? Thank you. >> Igal >> > > So, a selenium browser test is failing to find an element in the User > Interface. Although I'm not familiar with how these tests are supposed to > look, it seems to me that the failure is happening because a webserver is not > started. Just prior to the "test failure", there is this line: > > *09:29:47* INFO:backend.ExternalWebserver:Not starting a webserver. >
_______________________________________________ Wikitech-l mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
