Seen in https://integration.wikimedia.org/ci/job/wmf-quibble-selenium-php81/5383/console for the test patch r1129873, full debug logs captured, build kept forever.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T388416 CI jobs failing with various timeouts (March 2025) | |||
| Declined | None | T389855 Selenium CI failure: Error in "Page.should be re-creatable" Error: Timeout of 60000ms exceeded |
Event Timeline
Comment Actions
The error is:
17:47:29 [0-6] 2025-03-24T17:47:29.993Z INFO devtools: COMMAND findElement("css selector", "#wpLoginAttempt")
17:47:30 [0-6] 2025-03-24T17:47:29.994Z INFO devtools: RESULT { 'element-6066-11e4-a52e-4f735466cecf': 'ELEMENT-13' }
17:47:30 [0-6] 2025-03-24T17:47:30.001Z INFO devtools: COMMAND elementClick("ELEMENT-13")
17:47:30 [0-6] 2025-03-24T17:47:30.053Z INFO devtools: RESULT null
17:48:29 [0-6] Error in "Page.should be re-creatable"
17:48:29 Error: Timeout of 60000ms exceeded. The execution in the test "Page should be re-creatable" took too long. Try to reduce the run time or increase your timeout for test specs (https://webdriver.io/docs/timeouts). (/workspace/src/tests/selenium/specs/page.js)
17:48:29 at createTimeoutError (/workspace/src/node_modules/mocha/lib/errors.js:498:15)
17:48:29 at Runnable._timeoutError (/workspace/src/node_modules/mocha/lib/runnable.js:429:10)
17:48:29 at Timeout.<anonymous> (/workspace/src/node_modules/mocha/lib/runnable.js:244:24)
17:48:29 at listOnTimeout (node:internal/timers:581:17)
17:48:29 at process.processTimers (node:internal/timers:519:7)
17:54:29 [0-6] 2025-03-24T17:54:29.189Z ERROR @wdio/local-runner: Failed launching test session: Error: Protocol error (Runtime.evaluate): Session closed. Most likely the page has been closed.
17:54:29 [0-6] at CDPSession.send (/workspace/src/node_modules/puppeteer-core/lib/cjs/puppeteer/common/Connection.js:218:35)
17:54:29 [0-6] at ExecutionContext._evaluateInternal (/workspace/src/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:166:18)
17:54:29 [0-6] at ExecutionContext.evaluate (/workspace/src/node_modules/puppeteer-core/lib/cjs/puppeteer/common/ExecutionContext.js:110:27)
17:54:29 [0-6] at DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:230:36)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 [0-6] at async DevToolsDriver.checkPendingNavigations (/workspace/src/node_modules/devtools/build/devtoolsdriver.js:251:9)
17:54:29 2025-03-24T17:54:29.225Z DEBUG @wdio/local-runner: Runner 0-6 finished with exit code 1
17:54:29 [0-6] FAILED in chrome - /tests/selenium/specs/page.js
17:54:29 2025-03-24T17:54:29.226Z INFO @wdio/cli:launcher: Run onWorkerEnd hook
17:54:29 2025-03-24T17:54:29.226Z INFO @wdio/cli:launcher: Run onComplete hookHowever, I'm going to close this task, considering that we've seen all sorts of oddities in selenium over the last couple weeks. These have mostly been investigated in T389536. We made a few changes such as updating the wdio packages and disabling GPU. So, I don't think it's worth investigating this isolated issue now. I marked the original build for deletion. If this happens again though, we can reopen the task.
Comment Actions
It is fun to see a stacktrace for checkPendingNavigations. As I was looking at issues in webdriver.io earlier today, I have found https://github.com/webdriverio/webdriverio/pull/6240 Fix checkPendingNavigations memory leak in devtools which also states it never time out.
We would need a stacktrace of some sort and it might be worth filing a task to instrumentalize debugging NodeJS :)