Perma Tier 2 toolkit/components/antitracking/test/browser/browser_blockingCookies.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -
Categories
(Testing :: Mochitest, defect)
Tracking
(firefox-esr60 unaffected, firefox-esr68 unaffected, firefox69 unaffected, firefox70 disabled, firefox71 fixed)
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox69 | --- | unaffected |
firefox70 | --- | disabled |
firefox71 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: marco)
References
(Regression)
Details
(Keywords: intermittent-failure, regression)
Attachments
(1 file)
Filed by: rgurzau [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=263804513&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/X0xhANZdS2CY2BPuafTiVQ/runs/0/artifacts/public/logs/live_backing.log
[task 2019-08-28T03:09:32.053Z] 03:09:32 INFO - TEST-PASS | toolkit/components/antitracking/test/browser/browser_blockingCookies.js | Checking cookie blocking notifications -
[task 2019-08-28T03:09:32.053Z] 03:09:32 INFO - Removing the tab
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - Leaving test bound
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - Entering test bound
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - Cleaning up.
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - Buffered messages logged at 03:09:31
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - Leaving test bound
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - Console message: [JavaScript Error: "uncaught exception: Object" {file: "resource://testing-common/PromiseTestUtils.jsm" line: 112}]
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - Buffered messages finished
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - TEST-UNEXPECTED-FAIL | toolkit/components/antitracking/test/browser/browser_blockingCookies.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - TEST-FAIL | toolkit/components/antitracking/test/browser/browser_blockingCookies.js | Assertion count 4 is greater than expected range 0-0 assertions. -
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - GECKO(10356) | MEMORY STAT | vsize 2104574MB | vsizeMaxContiguous 65308873MB | residentFast 421MB | heapAllocated 81MB
[task 2019-08-28T03:09:32.054Z] 03:09:32 INFO - TEST-OK | toolkit/components/antitracking/test/browser/browser_blockingCookies.js | took 535077ms
Comment hidden (Intermittent Failures Robot) |
Comment 2•5 years ago
|
||
Bug 1576369 just landed a couple of days ago, let's give this a few days.
Comment 4•5 years ago
|
||
OK, so this failure affects windows10-64-ccov only. And if impacts many tests in this directory.
I am not going to chase the individual test timeouts in this directory. I believe the right fix here is to adjust the mochitest suite timeout accordingly for ccov tests which seem to run a lot more slowly.
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 8•5 years ago
|
||
Is there a way to change the timeout for all the tests in a directory?
Comment 9•5 years ago
|
||
For browser-chrome tests like this, the only way I can think of is to call requestLongerTimeout from code common to all the tests, like
Comment hidden (Intermittent Failures Robot) |
Assignee | ||
Comment 11•5 years ago
|
||
Updated•5 years ago
|
Comment 12•5 years ago
|
||
Comment 13•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•5 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•3 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Description
•