Intermittent [tier2] dom/ipc/tests/browser_gc_schedule.js | GC can begin on tab 1 - Got +0, expected null
Categories
(Core :: DOM: Content Processes, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox88 | --- | unaffected |
firefox89 | --- | unaffected |
firefox90 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: pbone)
References
(Regression)
Details
(Keywords: intermittent-failure, regression)
Attachments
(1 file)
Filed by: dluca [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=339472581&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/fUtOsM_MTc2LNyGmoQE-JA/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/fUtOsM_MTc2LNyGmoQE-JA/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | Unsorted events, last: 1620804474478, this: 1620804474540 -
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - Buffered messages finished
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_gc_schedule.js | GC can begin on tab 1 - Got +0, expected null
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - Stack trace:
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - chrome://mochikit/content/browser-test.js:test_is:1362
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - chrome://mochitests/content/browser/dom/ipc/tests/browser_gc_schedule.js:checkOneAtATime:107
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - chrome://mochitests/content/browser/dom/ipc/tests/browser_gc_schedule.js:gcAbort:251
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | event.state is good -
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | event.tab exists -
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | Unsorted events, last: 1620804474540, this: 1620804474577 -
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - Not taking screenshot here: see the one that was previously logged
[task 2021-05-12T07:27:54.737Z] 07:27:54 INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_gc_schedule.js | GC can end on tab 0 - Got +0, expected 1
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - Stack trace:
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - chrome://mochikit/content/browser-test.js:test_is:1362
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - chrome://mochitests/content/browser/dom/ipc/tests/browser_gc_schedule.js:checkOneAtATime:110
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - chrome://mochitests/content/browser/dom/ipc/tests/browser_gc_schedule.js:gcAbort:251
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | event.state is good -
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | event.tab exists -
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | Unsorted events, last: 1620804474577, this: 1620804474589 -
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - Not taking screenshot here: see the one that was previously logged
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - TEST-UNEXPECTED-FAIL | dom/ipc/tests/browser_gc_schedule.js | GC can end on tab 1 - Got 1, expected null
[task 2021-05-12T07:27:54.738Z] 07:27:54 INFO - Stack trace:
[task 2021-05-12T07:27:54.739Z] 07:27:54 INFO - chrome://mochikit/content/browser-test.js:test_is:1362
[task 2021-05-12T07:27:54.739Z] 07:27:54 INFO - chrome://mochitests/content/browser/dom/ipc/tests/browser_gc_schedule.js:checkOneAtATime:110
[task 2021-05-12T07:27:54.739Z] 07:27:54 INFO - chrome://mochitests/content/browser/dom/ipc/tests/browser_gc_schedule.js:gcAbort:251
[task 2021-05-12T07:27:54.739Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | No GC left running -
[task 2021-05-12T07:27:54.739Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | Tab 0 did a GC -
[task 2021-05-12T07:27:54.739Z] 07:27:54 INFO - TEST-PASS | dom/ipc/tests/browser_gc_schedule.js | Tab 1 did a GC -
[task 2021-05-12T07:27:54.739Z] 07:27:54 INFO - Leaving test bound gcAbort```
Paul, you should keep an eye on this in case the failure rate is too high. I'm assuming this is a test added for your patch.
Assignee | ||
Comment 2•4 years ago
|
||
Yes, this is a test I've added.
This is failing on "Windows 10 x64 WebRender debug test-windows10-64-qr/debug-test-verify-fis-e10s". What does "verify" mean here? why is this tier 2? I want to figure out if there's something about how the browser is run here that causes my test to fail, I was never able to make it fail when running locally or on try.
Comment 3•4 years ago
|
||
Set release status flags based on info from the regressing bug 1629064
(In reply to Paul Bone [:pbone] from comment #2)
This is failing on "Windows 10 x64 WebRender debug test-windows10-64-qr/debug-test-verify-fis-e10s". What does "verify" mean here? why is this tier 2? I want to figure out if there's something about how the browser is run here that causes my test to fail, I was never able to make it fail when running locally or on try.
"Verify mode" runs the test over and over again, by itself, in a variety of configurations including with chaos mode. You can run it locally like this with --verify.
Updated•4 years ago
|
If you dig through the logs, you might be able to figure out which specific part of the verify process was running when it failed.
Assignee | ||
Comment 6•4 years ago
|
||
I don't think the intermittent failures here are an indication of a true
problem here, more of a problem with how it's possible to test this code.
Updated•4 years ago
|
Comment 8•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Description
•