Perma fission browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js | Test timed out -
Categories
(Firefox :: Protections UI, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox69 | --- | unaffected |
firefox70 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: jwatt)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: intermittent-failure, regression, Whiteboard: [retriggered])
Filed by: csabou [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=263316378&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/C_e5hcQiQAqrX1kKy1s9xg/runs/0/artifacts/public/logs/live_backing.log
[task 2019-08-24T11:11:18.121Z] 11:11:18 INFO - TEST-PASS | browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js | Shows an exception when appropriate -
[task 2019-08-24T11:11:18.121Z] 11:11:18 INFO - Buffered messages finished
[task 2019-08-24T11:11:18.121Z] 11:11:18 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js | Test timed out -
[task 2019-08-24T11:11:18.121Z] 11:11:18 INFO - GECKO(8248) | JavaScript error: resource://testing-common/PromiseTestUtils.jsm, line 112: uncaught exception: Object
[task 2019-08-24T11:11:18.122Z] 11:11:18 INFO - Console message: [JavaScript Error: "uncaught exception: Object" {file: "resource://testing-common/PromiseTestUtils.jsm" line: 112}]
[task 2019-08-24T11:11:18.122Z] 11:11:18 INFO - GECKO(8248) | MEMORY STAT | vsize 2104126MB | vsizeMaxContiguous 65239989MB | residentFast 247MB | heapAllocated 88MB
[task 2019-08-24T11:11:18.122Z] 11:11:18 INFO - TEST-OK | browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js | took 45074ms
[task 2019-08-24T11:11:18.122Z] 11:11:18 INFO - Not taking screenshot here: see the one that was previously logged
Comment 1•5 years ago
|
||
This started with this merge to central: https://hg.mozilla.org/mozilla-central/pushloghtml?changeset=ea3eebc73ccb07ce574044b7063b95a309fc0933
and it's from Bug 1575273. Mike, could you please take a look?
Comment hidden (Intermittent Failures Robot) |
Updated•5 years ago
|
Comment 3•5 years ago
|
||
I am able to recreate this with my code removed as well.
It's timing out connecting to trackertest.org.
This can be recreated locally with:
./mach test --enable-fission browser/base/content/test/trackingUI/browser_trackingUI_cryptominers.js --verify
My code would definitely not affect this as it only comes into play when a policy is enabled.
We think this is bug 1559841
Updated•5 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment 5•5 years ago
|
||
This was fixed by the backout of the patch from bug 1559841 on Aug 28th.
Updated•5 years ago
|
![]() |
Assignee | |
Comment 6•5 years ago
|
||
FWIW this went away after making the changes Nika suggested in bug 1576413.
Comment 7•5 years ago
|
||
Retroactively moving fixed bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to an appropriate Fission Milestone.
This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:
0ee3c76a-bc79-4eb2-8d12-05dc0b68e732
Updated•3 years ago
|
Description
•