Intermittent fetch/same-http-downgrade.no-redirect.https.html.ini WPT CRASH with Fission
Categories
(Core :: DOM: Networking, defect, P3)
Tracking
()
People
(Reporter: cpeterson, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
if (os == "linux") and debug and webrender and fission: ["OK", "CRASH"]
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
.
Updated•5 years ago
|
Reporter | ||
Comment 2•5 years ago
|
||
Tracking WPT Fission bugs for Fission M6b (Q2)
Comment 3•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3
(Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3
(normal.)
So this test was merged with the other tests in upgrade-insecure-requests/gen/srcdoc-inherit.meta/upgrade/fetch/*
in web-platform-tests/wpt#22294 (pushed to m-c in bug 1623048, the meta file from comment #0 was also removed in that bug). The merged test is upgrade-insecure-requests/gen/srcdoc-inherit.meta/upgrade/fetch.https.html
.
There's no ini file for this new test, so I guess we haven't seen it crash or fail since being introduced. This could mean the crash was fixed, or just that it was rare enough that we haven't seen it yet. It's been about 2 months since that happened, so I'm closing this bug, we should open a new one if the crash re-appears.
Updated•4 years ago
|
Description
•