Intermittent TV devtools/client/webconsole/test/browser/browser_console_modes.js | reportError message from content process is only displayed once - Got 2, expected 1
Categories
(DevTools :: Console, defect, P5)
Tracking
(firefox-esr91 unaffected, firefox-esr102 unaffected, firefox103 unaffected, firefox104 unaffected, firefox105 fixed)
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox-esr102 | --- | unaffected |
firefox103 | --- | unaffected |
firefox104 | --- | unaffected |
firefox105 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: nchevobbe)
References
(Regression)
Details
(Keywords: intermittent-failure, regression)
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Filed by: ctuns [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=385989260&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/EY3ftjV5QE-vSd-UoLmqNQ/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/EY3ftjV5QE-vSd-UoLmqNQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
[task 2022-08-01T10:04:22.319Z] 10:04:22 INFO - TEST-PASS | devtools/client/webconsole/test/browser/browser_console_modes.js | "console.table()" is visible -
[task 2022-08-01T10:04:22.322Z] 10:04:22 INFO - Buffered messages finished
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - TEST-UNEXPECTED-FAIL | devtools/client/webconsole/test/browser/browser_console_modes.js | reportError message from content process is only displayed once - Got 2, expected 1
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - Stack trace:
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - chrome://mochikit/content/browser-test.js:test_is:1441
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - chrome://mochitests/content/browser/devtools/client/webconsole/test/browser/browser_console_modes.js:checkMessages:302
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - chrome://mochitests/content/browser/devtools/client/webconsole/test/browser/browser_console_modes.js:null:49
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - chrome://mochikit/content/browser-test.js:handleTask:1001
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - chrome://mochikit/content/browser-test.js:_runTaskBasedTest:1073
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - chrome://mochikit/content/browser-test.js:Tester_execTest:1208
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - chrome://mochikit/content/browser-test.js:nextTest/<:984
[task 2022-08-01T10:04:22.324Z] 10:04:22 INFO - chrome://mochikit/content/tests/SimpleTest/SimpleTest.js:SimpleTest.waitForFocus/<:1038
[task 2022-08-01T10:04:22.325Z] 10:04:22 INFO - TEST-PASS | devtools/client/webconsole/test/browser/browser_console_modes.js | Browser Console window title was updated again -
Comment 1•2 years ago
|
||
:nchevobbe, since you are the author of the regressor, bug 1776853, could you take a look?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 2•2 years ago
|
||
In the test, when fission isn't supported, we use Cu.reportError within
a SpecialPowers task, which puts the message in the console service cache.
If the test runs multiple time, the next iteration will run the test
with Fission support, which will consume cached messages, making the reportError
message appears more than we want.
This isn't a problem we can face in normal usage as when Fission is not supported,
we don't retrieve cached messages.
In order to fix the test failure, we simply clear the console service cache from
the content process.
Depends on D153327
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Set release status flags based on info from the regressing bug 1776853
Comment 5•2 years ago
|
||
bugherder |
Assignee | ||
Updated•2 years ago
|
Comment hidden (Intermittent Failures Robot) |
Description
•