Jobs:
View:
Phabricator search for related tasks:
Description
Description
Details
Details
Related Changes in Gerrit:
Event Timeline
There are a very large number of changes, so older changes are hidden. Show Older Changes
Comment Actions
Change #1020215 merged by jenkins-bot:
[mediawiki/core@master] selenium: Fix selenium-daily-beta(commons)-MediaWiki Jenkins jobs
Comment Actions
Change #1078686 had a related patch set uploaded (by Zfilipin; author: Zfilipin):
[mediawiki/core@master] WIP selenium: Fix 'Page should be editable'
Comment Actions
Change #1078686 merged by jenkins-bot:
[mediawiki/core@master] selenium: Fix 'Page should be editable'
Comment Actions
Change #1082215 had a related patch set uploaded (by Zfilipin; author: Zfilipin):
[mediawiki/core@master] WIP selenium: Fix Page should be undoable
Comment Actions
Change #1082215 merged by jenkins-bot:
[mediawiki/core@master] selenium: Fix 'Page should be undoable'
Comment Actions
https://integration.wikimedia.org/ci/job/selenium-daily-beta-MediaWiki/2547/
Test Result 7 failures (+7) 9 tests (+4) Took 1 min 28 sec. Add description All Failed Tests Test Name Duration Age chrome.136_0_0_0.linux.Page.should be previewable @daily 15 sec 1 chrome.136_0_0_0.linux.Page.should be editable @daily 9.6 sec 1 chrome.136_0_0_0.linux.Page.should have history @daily 8.4 sec 1 chrome.136_0_0_0.linux.Page.should be undoable @daily 12 sec 1 chrome.136_0_0_0.linux.Page.should be previewable @daily 12 sec 1 chrome.136_0_0_0.linux.Page.should be editable @daily 9.7 sec 1 chrome.136_0_0_0.linux.Page.should have history @daily 8.2 sec 1
Comment Actions
Thanks @bd808, I don't spend any time on debugging unless the job fails at least two days in a row. The most usual reason the job fails, by far, is a problem with the beta cluster. The job usually passes when it is rerun. I have just checked, it has failed yesterday but passed today, so I don't think there's a problem.
Comment Actions
https://integration.wikimedia.org/ci/job/selenium-daily-betacommons-MediaWiki/2235/ seems to have a reporting failure more than a test failure?
01:22:50 Execution of 10 workers started at 2025-06-10T01:22:50.806Z 01:22:50 01:23:01 [0-6] RUNNING in chrome - file:///tests/selenium/specs/page.js 01:23:43 [0-6] PASSED in chrome - file:///tests/selenium/specs/page.js 01:23:48 [0-9] RUNNING in chrome - file:///tests/selenium/wdio-mediawiki/specs/BlankPage.js 01:23:51 [0-9] PASSED in chrome - file:///tests/selenium/wdio-mediawiki/specs/BlankPage.js 01:23:51 01:23:51 "spec" Reporter: 01:23:51 ------------------------------------------------------------------ 01:23:51 [chrome 136.0.7103.92 linux #0-6] Running: chrome (v136.0.7103.92) on linux 01:23:51 [chrome 136.0.7103.92 linux #0-6] Session ID: 38fa0d02793d4d25141b6d4e80dcc526 01:23:51 [chrome 136.0.7103.92 linux #0-6] 01:23:51 [chrome 136.0.7103.92 linux #0-6] » tests/selenium/specs/page.js 01:23:51 [chrome 136.0.7103.92 linux #0-6] Page 01:23:51 [chrome 136.0.7103.92 linux #0-6] ✓ should be previewable @daily 01:23:51 [chrome 136.0.7103.92 linux #0-6] ✓ should be editable @daily 01:23:51 [chrome 136.0.7103.92 linux #0-6] ✓ should have history @daily 01:23:51 [chrome 136.0.7103.92 linux #0-6] ✓ should be undoable @daily 01:23:51 [chrome 136.0.7103.92 linux #0-6] 01:23:51 [chrome 136.0.7103.92 linux #0-6] 4 passing (36.1s) 01:23:51 ------------------------------------------------------------------ 01:23:51 [chrome 136.0.7103.92 linux #0-9] Running: chrome (v136.0.7103.92) on linux 01:23:51 [chrome 136.0.7103.92 linux #0-9] Session ID: 9109f3c1d88a98f29730d16a64ce1cd4 01:23:51 [chrome 136.0.7103.92 linux #0-9] 01:23:51 [chrome 136.0.7103.92 linux #0-9] » tests/selenium/wdio-mediawiki/specs/BlankPage.js 01:23:51 [chrome 136.0.7103.92 linux #0-9] BlankPage 01:23:51 [chrome 136.0.7103.92 linux #0-9] ✓ should have its title @daily 01:23:51 [chrome 136.0.7103.92 linux #0-9] 01:23:51 [chrome 136.0.7103.92 linux #0-9] 1 passing (996ms) 01:23:51 01:23:51 01:23:51 Spec Files: 2 passed, 8 skipped, 10 total (100% completed) in 00:01:00
Comment Actions
I have just noticed that. I don't understand why the jobs are failing, since all tests passed.
Both selenium-daily-beta-MediaWiki/2573 and selenium-daily-betacommons-MediaWiki/2235 have no failures.
09:40:49 Execution of 10 workers started at 2025-06-10T07:40:49.101Z 09:40:49 09:40:59 [0-6] RUNNING in chrome - file:///tests/selenium/specs/page.js 09:41:38 [0-6] PASSED in chrome - file:///tests/selenium/specs/page.js 09:41:43 [0-9] RUNNING in chrome - file:///tests/selenium/wdio-mediawiki/specs/BlankPage.js 09:41:45 [0-9] PASSED in chrome - file:///tests/selenium/wdio-mediawiki/specs/BlankPage.js 09:41:45 09:41:45 "spec" Reporter: 09:41:45 ------------------------------------------------------------------ 09:41:45 [chrome 136.0.7103.92 linux #0-6] Running: chrome (v136.0.7103.92) on linux 09:41:45 [chrome 136.0.7103.92 linux #0-6] Session ID: 7fd39b4487d3deaf24a2a05aa85b374c 09:41:45 [chrome 136.0.7103.92 linux #0-6] 09:41:45 [chrome 136.0.7103.92 linux #0-6] » tests/selenium/specs/page.js 09:41:45 [chrome 136.0.7103.92 linux #0-6] Page 09:41:45 [chrome 136.0.7103.92 linux #0-6] ✓ should be previewable @daily 09:41:45 [chrome 136.0.7103.92 linux #0-6] ✓ should be editable @daily 09:41:45 [chrome 136.0.7103.92 linux #0-6] ✓ should have history @daily 09:41:45 [chrome 136.0.7103.92 linux #0-6] ✓ should be undoable @daily 09:41:45 [chrome 136.0.7103.92 linux #0-6] 09:41:45 [chrome 136.0.7103.92 linux #0-6] 4 passing (33.6s) 09:41:45 ------------------------------------------------------------------ 09:41:45 [chrome 136.0.7103.92 linux #0-9] Running: chrome (v136.0.7103.92) on linux 09:41:45 [chrome 136.0.7103.92 linux #0-9] Session ID: fd779208c12ababd0274dbedb7753407 09:41:45 [chrome 136.0.7103.92 linux #0-9] 09:41:45 [chrome 136.0.7103.92 linux #0-9] » tests/selenium/wdio-mediawiki/specs/BlankPage.js 09:41:45 [chrome 136.0.7103.92 linux #0-9] BlankPage 09:41:45 [chrome 136.0.7103.92 linux #0-9] ✓ should have its title @daily 09:41:45 [chrome 136.0.7103.92 linux #0-9] 09:41:45 [chrome 136.0.7103.92 linux #0-9] 1 passing (889ms) 09:41:45 09:41:45 09:41:45 Spec Files: 2 passed, 8 skipped, 10 total (100% completed) in 00:00:56
Comment Actions
The WDIO.xunit-*.xml output files are telling a slightly different story. In https://integration.wikimedia.org/ci/job/selenium-daily-beta-MediaWiki/2574/artifact/log/ there are 8 of 10 test result files that look something like:
WDIO.xunit-2025-06-11T07-41-11-028Z-ea1b38a7.xml
<?xml version="1.0" encoding="UTF-8"?> <testsuites tests="1" failures="1" errors="0" skipped="0"> <testsuite tests="1" failures="1" errors="0" skipped="0"> <testcase classname="" name=""> <failure message="No tests found"/> </testcase> </testsuite> </testsuites>
The last green test result was https://integration.wikimedia.org/ci/job/selenium-daily-beta-MediaWiki/2567/. It has 8 of 10 test result files that look something like:
WDIO.xunit-2025-06-04T07-40-51-894Z-4dca3c97.xml
<?xml version="1.0" encoding="UTF-8"?> <testsuites tests="0" failures="0" errors="0" skipped="0"/>
Something changed in the test execution between the 2025-06-04 run and the 2025-06-05 run that made the WDIO.xunit-*.xml reports for empty test suites report as an explicit failure. The "Publish JUnit test result report" step in the job definition has "Do not fail the build on empty test results" enabled, but the newer results are explicitly marked as containing a failed test rather than the prior behavior of reporting an empty testsuite.
Comment Actions
We have upgraded core from wdio v8 to v9 on 2025-06-04.
https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1151218
I will create a new task to track the problem. This task is an epic to keep to jobs green.
Thanks for reporting this.