Fix browser_download_idn_blocklist.js test with HTTPS first
Categories
(Core :: DOM: Security, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: simonf, Assigned: simonf)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file, 1 obsolete file)
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
r=maltejur,freddyb,ckerschb
For HTTPS first we want to treat NS_ERROR_UNKNOWN_HOST as an HTTPS
related error because it might be a 404 returned by a proxy (see
HttpProxyResponseToErrorCode). For the HTTPS-only case we don't want
that because it almost always is an unrelated error and the users would
have to confirm the interstitial every time to find out.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Backed out for causing xpcshell failures in test_ext_dnr_private_browsing.js.
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-TIMEOUT | xpcshell-remote.toml:toolkit/components/extensions/test/xpcshell/test_ext_dnr_private_browsing.js | Test timed out
Assignee | ||
Comment 4•1 year ago
|
||
This test failure seems unrelated to my change and the test completes fine in about 7 seconds on my machine. Should I just re-land?
Assignee | ||
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Hi! As I pointed in Comment 3 there were several xpcshell failures that seemed to be started once your changeset landed on Autoland. Here you can see once again that there are several failures that started from your changeset and seemed to be resolved by the backout. Note that the failures seem to happen frequent (not perma) and only on Windows and Linux. If you are sure that this will not replicate once again, you can re-land but will be backout again otherwise.
Comment 6•1 year ago
|
||
FWIW, I think this might be an unrealted timeout. I just retriggered the test job within the push at https://treeherder.mozilla.org/jobs?repo=autoland&selectedJob=457500123&revision=c07ec5ce9aa1d890134ffb93e07d7d0335f27378. Let's see if it keeps failing.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 7•1 year ago
|
||
Disabling HTTPS-First for now since we can neither reliably fall back nor use an HTTPS server.
Assignee | ||
Comment 8•1 year ago
|
||
Comment 10•1 year ago
|
||
bugherder |
Updated•2 months ago
|
Description
•