Permafailing xpcshell No tests run or test summary not found - all tests are skipped in dom/webtransport/test/xpcshell/test_*
Categories
(Testing :: XPCShell Harness, defect, P5)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Unassigned)
Details
(Keywords: intermittent-failure)
Filed by: ncsoregi [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=423774125&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/FkW-yKa-RS-e09SBQW0ZgQ/runs/0/artifacts/public/logs/live_backing.log
[task 2023-07-25T05:10:33.076Z] 05:10:33 INFO - runxpcshelltests.py | using symbolizer at /builds/worker/workspace/build/application/firefox/llvm-symbolizer
[task 2023-07-25T05:10:33.076Z] 05:10:33 INFO - Found node at /builds/worker/fetches/node/bin/node
[task 2023-07-25T05:10:33.076Z] 05:10:33 INFO - Found moz-http2 at /builds/worker/workspace/build/tests/xpcshell/moz-http2/moz-http2.js
[task 2023-07-25T05:10:33.141Z] 05:10:33 INFO - mozserve | Found Http3Server path: /builds/worker/workspace/build/application/firefox/http3server
[task 2023-07-25T05:10:33.142Z] 05:10:33 INFO - mozserve | cert db path: /builds/worker/workspace/build/tests/xpcshell/http3server/http3serverDB
[task 2023-07-25T05:10:33.163Z] 05:10:33 INFO - mozserve | http3 server msg: HTTP3 server listening on ports 57971, 35572, 36237, 47011 and 50300. EchConfig is @AE3+DQBJBwAgACDPR1jTMUiYV3AKOopbdGtCxWF8j3JaFHGU067uiTVuHQAQAAEAAQABAAMAAgABAAIAA0AOcHVibGljLmV4YW1wbGUAAA==@
[task 2023-07-25T05:10:33.386Z] 05:10:33 INFO - Using at most 4 threads.
[task 2023-07-25T05:10:33.386Z] 05:10:33 INFO - SUITE-START | Running 3 tests
[task 2023-07-25T05:10:33.387Z] 05:10:33 INFO - TEST-START | dom/webtransport/test/xpcshell/test_close.js
[task 2023-07-25T05:10:33.387Z] 05:10:33 INFO - TEST-SKIP | dom/webtransport/test/xpcshell/test_close.js | took 0ms
[task 2023-07-25T05:10:33.388Z] 05:10:33 INFO - TEST-START | dom/webtransport/test/xpcshell/test_simple_conn.js
[task 2023-07-25T05:10:33.388Z] 05:10:33 INFO - TEST-SKIP | dom/webtransport/test/xpcshell/test_simple_conn.js | took 0ms
[task 2023-07-25T05:10:33.389Z] 05:10:33 INFO - TEST-START | dom/webtransport/test/xpcshell/test_simple_stream.js
[task 2023-07-25T05:10:33.390Z] 05:10:33 INFO - TEST-SKIP | dom/webtransport/test/xpcshell/test_simple_stream.js | took 0ms
[task 2023-07-25T05:10:33.390Z] 05:10:33 INFO - Retrying tests that failed when run in parallel.
[task 2023-07-25T05:10:33.390Z] 05:10:33 INFO - TEST-START | dom/webtransport/test/xpcshell/test_simple_conn.js
[task 2023-07-25T05:10:33.391Z] 05:10:33 INFO - TEST-SKIP | dom/webtransport/test/xpcshell/test_simple_conn.js | took 1ms
[task 2023-07-25T05:10:33.391Z] 05:10:33 INFO - TEST-START | dom/webtransport/test/xpcshell/test_simple_stream.js
[task 2023-07-25T05:10:33.392Z] 05:10:33 INFO - TEST-SKIP | dom/webtransport/test/xpcshell/test_simple_stream.js | took 0ms
[task 2023-07-25T05:10:33.392Z] 05:10:33 INFO - INFO | Result summary:
[task 2023-07-25T05:10:33.393Z] 05:10:33 INFO - INFO | Passed: 0
[task 2023-07-25T05:10:33.393Z] 05:10:33 INFO - INFO | Failed: 0
[task 2023-07-25T05:10:33.393Z] 05:10:33 INFO - INFO | Todo: 0
[task 2023-07-25T05:10:33.393Z] 05:10:33 INFO - INFO | Retried: 2
[task 2023-07-25T05:10:33.394Z] 05:10:33 INFO - SUITE-END | took 0s
[task 2023-07-25T05:10:33.394Z] 05:10:33 INFO - Node moz-http2 server shutting down ...
[task 2023-07-25T05:10:33.394Z] 05:10:33 INFO - http3Server server shutting down ...
[task 2023-07-25T05:10:33.518Z] 05:10:33 INFO - Return code: 0
[task 2023-07-25T05:10:33.518Z] 05:10:33 ERROR - No tests run or test summary not found
[task 2023-07-25T05:10:33.518Z] 05:10:33 INFO - TinderboxPrint: xpcshell-xpcshell<br/><em class="testfail">T-FAIL</em>
[task 2023-07-25T05:10:33.518Z] 05:10:33 WARNING - setting return code to 1
Comment 1•3 years ago
|
||
:marco, somehow we are scheduling this with mozci- in this specific case, for linux/asan xpcshell spi-nw-nofis, we only schedule dom/webtransport/test/xpcshell which is not supported on spi-nw variant.
I am not sure how that directory matches up with the change to only taskcluster/gecko_taskgraph/actions/confirm_failure.py in that push.
I guess we should figure out:
- why this is called for that change (and apparently a few others)
- how can we future proof this?
Comment 2•3 years ago
|
||
I vaguely remember similar bugs in the past, the fix was in-tree. It is not strictly related to bugbug, as a normal user could also get into this situation by trying to schedule that test on that platform. It should not be possible to do it.
Maybe :ahal remembers what the earlier fixes were.
Comment 3•3 years ago
|
||
I think you're thinking of the "guessed mozinfo" being mismatched with reality? That sounds plausible, though Joel's also well aware of that problem (he recently landed a fix to future proof it a little more).
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 13•3 years ago
|
||
https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.
Description
•