https://searchfox.org/mozilla-central/source/testing/web-platform/meta/navigation-timing/dom_interactive_media_document.html.ini

if webrender and fission and (os == "win") and not debug: ["OK", "TIMEOUT"]
if webrender and fission and (os == "win") and not debug: ["PASS", "NOTRUN"]

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.

I will take a look.

This test seems being fixed already on the try server [1], it would be tested in wpt1 and I didn't see any its failure. We can try to renable it.

[1] https://treeherder.mozilla.org/#/jobs?repo=try&revision=ac94cbe57d3ac8eb8ac2a274a6dcd16989964820&selectedJob=294975468

This test seems being fixed already and there is no any failure on on the try server [1] (it would be tested in wpt1), so I think it's time to enable this test.

[1] https://treeherder.mozilla.org/#/jobs?repo=try&revision=ac94cbe57d3ac8eb8ac2a274a6dcd16989964820&selectedJob=294975468

https://hg.mozilla.org/mozilla-central/rev/f64d7850ce54