run mochitest-remote in fission everywhere
Categories
(Remote Protocol :: CDP, task, P3)
Tracking
(firefox98 fixed)
| Tracking | Status | |
|---|---|---|
| firefox98 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
Attachments
(1 file, 1 obsolete file)
now that fission is default for desktop, we need to run our tests in fission everywhere.
linux/debug: m/m-swr/m-spi-nw -> fis
linux/ship: m/m-spi-nw -> fis
linux/asan: m -> fis
linux/ccov: m -> fis
osx/debug: m-spi-nw -> fis
osx/ship: m-spi-nw -> fis
win32/debug: m -> fis
win32/ship: m -> fis
win10/ccov: m -> fis
win10/debug: m/m-spi-nw -> fis
win10/asan: m -> fis
win10/ship: m/m-spi-nw -> fis
we have some failures to look at, specifically on linux/[opt|debug|asan]:
https://treeherder.mozilla.org/jobs?repo=try&tier=1%2C2%2C3&revision=761aca33b329c33843bef39178ec5e39d491297e
all failures look to be:
TEST-UNEXPECTED-FAIL | remote/cdp/test/browser/runtime/browser_executionContextEvents.js | Received Runtime context events in expected order - ["Runtime.executionContextDestroyed","Runtime.executionContextsCleared","Runtime.executionContextCreated","Runtime.executionContextDestroyed"] deepEqual ["Runtime.executionContextDestroyed","Runtime.executionContextsCleared","Runtime.executionContextDestroyed","Runtime.executionContextCreated"] - JS fram
| Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 2•4 years ago
|
||
Joel, the failing test was disabled for now. I assume that we can continue on this bug?
Updated•4 years ago
|
| Assignee | ||
Comment 3•4 years ago
|
||
thanks for letting me know, let me run on try and see where we end up.
| Assignee | ||
Comment 4•4 years ago
|
||
Comment 6•4 years ago
|
||
| bugherder | ||
Updated•4 years ago
|
Description
•