Intermittent unhandled-promise-rejections/promise-rejection-events.html.ini WPT TIMEOUT with Fission
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: cpeterson, Assigned: edgar)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
if (os == "linux") and webrender and not debug and fission: ["OK", "TIMEOUT"]
if (os == 'linux' and os_version == '18.04') and not debug and fission: ["OK", "TIMEOUT"] # Bug 1607867
if (os == "linux") and webrender and not debug and fission: ["PASS", "TIMEOUT"]
Updated•5 years ago
|
Reporter | ||
Comment 1•5 years ago
|
||
The DOM Fission team is relying on feature teams to debug and fix Fission failures in their tests. If the failure looks like a bug in Fission's DOM or IPC changes, you can send the bug back to me.
We're hoping to enable Fission for a subset of Nightly users in early Q3, so we would like WPT tests to be green for Fission by end of Q2. Whether a particular test failure actually blocks shipping Fission is up to the discretion of the feature team. You all would know better than the DOM Fission which test failures are most important.
You can enable Fission when running WPT tests locally using mach wpt --enable-fission
.
Comment 2•5 years ago
|
||
Hi Edgar, please help us to understand the importance and priority if you see fit, thanks.
Assignee | ||
Comment 3•5 years ago
|
||
Could not reproduce the timeout on try with 100+ retriggering, I think we could enable it back to see how it goes now.
https://treeherder.mozilla.org/?#/jobs?repo=try&group_state=expanded&revision=a6eb96d50b600f989ade7b6f6fcf25b84b2b2b01&searchStr=w-fis%2Copt%2Cwpt12&selectedJob=294327857 (the only failure is from MediaRecorder-destroy-script-execution.html).
Assignee | ||
Comment 4•5 years ago
|
||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
bugherder |
Description
•