Perma linux1804 asan FATAL ERROR: Non-local network connections are disabled and a connection attempt to example.com (23.192.228.80) was made. | single tracking bug
Categories
(Core :: DOM: Security, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr128 | --- | unaffected |
firefox134 | --- | unaffected |
firefox135 | --- | unaffected |
firefox136 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: freddy)
References
(Regression, )
Details
(Keywords: intermittent-failure, regression, Whiteboard: [domsecurity-intermittent], [wptsync upstream])
Attachments
(1 file)
Filed by: hskupin [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=489818239&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/LHoIjBCiRM2HOZxjERT4VA/runs/0/artifacts/public/logs/live_backing.log
[task 2025-01-13T00:50:18.876Z] 00:50:18 INFO - TEST-START | /sanitizer-api/sethtml-tree-construction.tentative.html
[task 2025-01-13T00:50:18.881Z] 00:50:18 INFO - Closing window fe8a86bd-de1d-4469-b6d9-dbbfbec6c0d4
[task 2025-01-13T00:50:18.888Z] 00:50:18 INFO - PID 6428 | FATAL ERROR: Non-local network connections are disabled and a connection attempt to bla.com (38.127.92.75) was made.
[task 2025-01-13T00:50:18.889Z] 00:50:18 INFO - PID 6428 | You should only access hostnames available via the test networking proxy (if running mochitests) or from a test-specific httpd.js server (if running xpcshell tests). Browser services should be disabled or redirected to a local server.
Comment 1•1 month ago
|
||
This is actually a regression from the wpt downstream sync from January 10th on bug 1938103. Freddy can you please take a look?
Updated•1 month ago
|
Comment 2•1 month ago
|
||
Set release status flags based on info from the regressing bug 1938103
Assignee | ||
Comment 3•1 month ago
|
||
That one looks simple. taking a look.
Assignee | ||
Updated•1 month ago
|
Assignee | ||
Comment 4•1 month ago
|
||
Ah, no. I thought there were new instances but this is a duplicate of https://github.com/web-platform-tests/wpt/pull/49867, which just needs merging.
Comment 5•1 month ago
|
||
This is still affecting our CI so we should keep it open until the mentioned PR has been fixed. That way we can track and classify test failures correctly. The downstream sync of this fix will happen via bug 1939700.
Assignee | ||
Comment 6•1 month ago
|
||
Why are there so many bugs for just one upstream change?
I am now counting four.
Comment 7•1 month ago
|
||
Bug 1938103 is the original wpt sync bug when the test changes were initially downstream synced. Then bug 1938984 was created by the wpt sync bot to inform the triage owner of a component of new failures. This bug should have as best been updated to reflect the actual failure that can be seen in CI. With your upstream fix on the wpt repository directly the crash will go away once bug 1939700 is landed by the sync bot.
Best here is when you just duplicate bug 1938984 against this one and all will be fine?
Comment hidden (Intermittent Failures Robot) |
Comment 10•1 month ago
|
||
This is still happening even after Bug 1939700 is fixed
Failure log: https://treeherder.mozilla.org/logviewer?job_id=490269403&repo=mozilla-central&lineNumber=12351
Comment hidden (Intermittent Failures Robot) |
Comment 12•1 month ago
|
||
Freddy, to make it easier it might be good to just provide a patch here on this bug, push it to try to verify that it works and get it landed. Then the wpt sync bot will run an upstream sync. That would as well be faster to get this failure fixed in our CI.
Assignee | ||
Comment 13•1 month ago
|
||
I just built from latest central a couple of minutes and ran the test locally, I saw no failures at all. I don't get it :|
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 16•1 month ago
|
||
Comment hidden (Intermittent Failures Robot) |
Updated•1 month ago
|
Comment 18•1 month ago
|
||
Comment 20•1 month ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Description
•