Fix and re-enable dom/tests/browser/browser_ConsoleStorageAPITests.js test for Fission
Categories
(DevTools :: General, task, P3)
Tracking
(Fission Milestone:M7a, firefox89 fixed)
Tracking | Status | |
---|---|---|
firefox89 | --- | fixed |
People
(Reporter: cpeterson, Assigned: nchevobbe)
References
(Blocks 2 open bugs)
Details
(Whiteboard: dt-fission-m3-mvp)
Attachments
(1 file)
This test was disabled for Fission in bug 1566182. This test was disabled for Linux ASan in bug 1614436.
[browser_ConsoleStorageAPITests.js]
skip-if = fission || (asan && os == "linux") # Bug 1614436
Updated•4 years ago
|
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
Tracking DevTools test bugs for Fission M8 (blocking Release experiment).
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 2•4 years ago
|
||
Tracking DevTools Post-M8 bugs for Fission MVP milestone. They don't block the Fission Release channel experiment, but we would like them to be completed before we roll out Fission by default.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 3•4 years ago
|
||
The test was doing a navigation from about:blank to an example.com URL in a
ContentTask, which I guess was going bad with fission enabled since we were
creating a new content process.
I don't think there was a good reason to do that, so we start the test directly
with the "final" URL.
And since about:blank page can be special, we use a data url instead.
A few info
calls are added to have better logs, and the test is slightly refactored
to be easier to follow.
Finally, the test was a bit loose, only checking the number of events we were
receiving. We take this opportunity to really check that we get the events that
are expected.
Comment 5•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Description
•