Fix and re-enable devtools/client/shared/test/browser_spectrum.js test for Fission
Categories
(DevTools :: General, task)
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 1568035, but it was already disabled for intermittent --verify failures in bug 1478156.
Does re-enabling this test need to block shipping Fission MVP?
[browser_spectrum.js]
skip-if =
verify # Bug 1478156 test verify fails on master
fission && debug # Fails intermittently.
|
Reporter | |
Updated•3 years ago
|
|
||
Updated•3 years ago
|
|
||
Updated•3 years ago
|
|
|
Reporter | |
Comment 1•3 years ago
|
||
Tracking DevTools test bugs for Fission M8 (blocking Release experiment).
|
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Comment 2•3 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•3 years ago
|
|
|
Assignee | |
Comment 3•3 years ago
|
||
The test failure doesn't seem to have anything to do with Fission,
but this might have introduce some changes in timings that would
trigger a race condition somehow.
The test was failing because in one of the test we were moving a slider
to change a color, while the slider element had a height of 0, which
would interfere with the computations that are done later.
Waiting for a tick before running the tests so the container is properly
rendered seems to do the trick.
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5c8e536a9b11 [devtools] Enable browser_spectrum.js on Fission. r=jdescottes.
|
||
Comment 5•3 years ago
|
||
| bugherder | ||
|
|
||
Updated•3 years ago
|
Description
•