Intermittent netwerk/test/unit/test_bug1378385_http1.js | single tracking bug
Categories
(Core :: Networking, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox140 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: kershaw)
Details
(Keywords: intermittent-testcase)
Attachments
(1 file)
Filed by: brennie [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=507237219&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/OCfFKv6kT4m8AdVlB_I-ag/runs/0/artifacts/public/logs/live_backing.log
Comment 1•7 months ago
|
||
netwerk/cookie/test/unit/test_migrateCookieLifetimePref.js | xpcshell return code: 0
netwerk/test/unit/test_bug1378385_http1.js | xpcshell return code: 0
netwerk/test/unit/test_bug1378385_http1.js | check_response_id - [check_response_id : 130] "123" == 126
widget/windows/tests/unit/test_windows_alert_service.js | xpcshell return code: 0
widget/windows/tests/unit/test_windows_alert_service.js | - when notification server pref is unset - ["<toast launch=\\"launch\\"><visual><binding template=\\"ToastText03\\"><text id=\\"1\\">title</text><text id=\\"2\\">text</text></binding></visual><actions><action content=\\"Notification settings\\"/></actions></toast>",{"launch":{"invalid key":"invalid value","action":"{\\"action\\":\\"\\"}"},"actions":{"Notification
[taskcluster:error] exit status 2
I was backed out for this in bug 1957513 but I believe this might be a ~perma fail that is intermittently passing? It is failing for me (and :edgul) on main.
Comment 2•7 months ago
•
|
||
This is green on central/main, link here. The changes in https://bugzilla.mozilla.org/show_bug.cgi?id=1957513#c14 cause this to permafail, proof here.
Comment 3•7 months ago
|
||
This is still failing locally. The necko team should investigate
Comment 4•7 months ago
|
||
If you run the entire test suite, the test seems to pass. When you run the test in isolation, it fails 100% of the time
| Assignee | ||
Comment 5•7 months ago
|
||
The issue is that in nsHttpHandler::PrefsChanged, we don't update mActiveTabPriority when the network.http.active_tab_priority changes.
As a result, this line becomes a no-op.
| Assignee | ||
Comment 6•7 months ago
|
||
Updated•7 months ago
|
Comment 9•6 months ago
|
||
Backed out for causing bustage at PendingTransactionQueue.cpp
| Assignee | ||
Comment 10•6 months ago
|
||
Comment 11•6 months ago
|
||
Comment 12•6 months ago
|
||
| bugherder | ||
Updated•6 months ago
|
Description
•