Intermittent dom/webtransport/test/xpcshell/test_close.js | single tracking bug
Categories
(Core :: DOM: Networking, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox137 | --- | unaffected |
firefox138 | --- | unaffected |
firefox139 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: heather)
References
(Regression)
Details
(Keywords: intermittent-failure, intermittent-testcase, regression)
Attachments
(1 file)
Filed by: heather [at] thunderbird.net
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=503862284&repo=comm-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/JGTjLAxNTceDxCnwyHw_iA/runs/0/artifacts/public/logs/live_backing.log
WARNING - TEST-UNEXPECTED-FAIL | dom/webtransport/test/xpcshell/test_close.js | xpcshell return code: 0
WARNING - TEST-UNEXPECTED-FAIL | dom/webtransport/test/xpcshell/test_close.js | setup - [setup : 44] "" != ""
Assignee | ||
Comment 1•13 days ago
|
||
I was looking at the failure "Windows 11 x64 22H2 WebRender Shippable - X-mix(X4)” and it is a new(ish) permafail since April 9. The first time it starts failing (same errors as we have today) could be related to an m-c change done that same day.
it looks like the test_close.js
is skipped for m-c treeherder runs, because of dom/webtransport/test/xpcshell/xpcshell.toml
. so why isn't it skipped for us? what version of windows 11 do we have in our CI? If it's different from os_version == '11.26100'
then is there a common way that we overwrite elements of m-c tests (in this case, to match if our windows version is different from m-c's)?
Comment 2•13 days ago
|
||
Set release status flags based on info from the regressing bug 1959284
:jmaher, since you are the author of the regressor, bug 1959284, could you take a look?
For more information, please visit BugBot documentation.
Comment 3•13 days ago
|
||
thanks for filing this- and sorry this turned into an issue for you. You made my job easy to figure this out.
In January we migrated our windows tests from the win11-64-2009
machines to win11-64-24h2
(see bug 1936396). the machines on comm-central are running the win11-64-2009
image which is os_version=='11.2009'
.
I found this by looking at a comm-central push and in the mochitest tasks we print out all of the variables (i.e. this log - search for os_version
).
2 choices here:
- update the conditions to skip on 2009. For this specific test it would be in the
[DEFAULT]
section at the top. - migrate to the 24h2 version of windows. This is the windows 11 Oct 2024 major update.
Assignee | ||
Comment 4•13 days ago
|
||
Updated•13 days ago
|
Assignee | ||
Comment 5•13 days ago
|
||
Thank you for the assistance! I've pushed a change to skip on windows os_version == 11.2009
.
Updated•13 days ago
|
Comment 7•12 days ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Description
•