Seen in https://integration.wikimedia.org/ci/job/quibble-vendor-mysql-php82-noselenium/32305/console (kept forever) for parsoid patch r1141191:
18:25:08 ve.ce.Document 18:25:08 ✔ Converter tests 18:25:12 07 05 2025 16:25:12.550:DEBUG [Firefox 128.0 (Linux x86_64)]: Disconnected during run, waiting 2000ms for reconnecting. 18:25:12 07 05 2025 16:25:12.551:DEBUG [Firefox 128.0 (Linux x86_64)]: EXECUTING -> EXECUTING_DISCONNECTED 18:25:13 07 05 2025 16:25:13.841:DEBUG [middleware:source-files]: Requesting /null 18:25:13 07 05 2025 16:25:13.841:DEBUG [middleware:source-files]: Fetching /null 18:25:13 07 05 2025 16:25:13.842:DEBUG [proxy]: proxying request - /null to 127.0.0.1:9413 18:25:14 07 05 2025 16:25:14.499:DEBUG [karma-server]: A browser has connected on socket 40x9O0AchJbo_BxxAAAD 18:25:14 07 05 2025 16:25:14.511:DEBUG [web-server]: upgrade /socket.io/?EIO=4&transport=websocket&sid=oxY1AMzFD1B70M0kAAAC 18:25:14 07 05 2025 16:25:14.511:DEBUG [proxy]: NOT upgrading proxyWebSocketRequest /socket.io/?EIO=4&transport=websocket&sid=oxY1AMzFD1B70M0kAAAC 18:25:14 07 05 2025 16:25:14.552:WARN [Firefox 128.0 (Linux x86_64)]: Disconnected (0 times) reconnect failed before timeout of 2000ms (ping timeout) 18:25:14 Firefox 128.0 (Linux x86_64) ERROR 18:25:14 Disconnected reconnect failed before timeout of 2000ms (ping timeout) 18:25:14 07 05 2025 16:25:14.552:DEBUG [Firefox 128.0 (Linux x86_64)]: EXECUTING_DISCONNECTED -> DISCONNECTED 18:25:14 07 05 2025 16:25:14.554:DEBUG [launcher]: CAPTURED -> BEING_KILLED 18:25:14 07 05 2025 16:25:14.558:DEBUG [launcher]: BEING_KILLED -> BEING_FORCE_KILLED 18:25:14 07 05 2025 16:25:14.558:DEBUG [Firefox 128.0 (Linux x86_64)]: DISCONNECTED -> DISCONNECTED 18:25:14 18:25:14 Finished in 23.186 secs / 16.741 secs @ 16:25:14 GMT+0000 (Coordinated Universal Time)
Seen similar errors in other builds and different tests, including reports in the parent task.
My guess is that this has nothing to do with VE (or any other specific component), and that CI executors sometimes have spikes of resource unavailability; because JavaScript-ish tests (QUnit, selenium, api-testing) run under strict timeouts, these spikes can result in test failure. If so, this would be similar to T380061 and T389863.