This is causing browser_httpResponseProcessSelection.js [1] to timeout when run with Fission enabled.

[1] https://searchfox.org/mozilla-central/rev/e7c61f4a68b974d5fecd216dc7407b631a24eb8f/toolkit/components/remotebrowserutils/tests/browser/browser_httpResponseProcessSelection.js#308-340

Tentatively moving all bugs whose summaries mention "Fission" (or other Fission-related keywords) but are not assigned to a Fission Milestone to the "?" triage milestone.

This will generate a lot of bugmail, so you can filter your bugmail for the following UUID and delete them en masse:

0ee3c76a-bc79-4eb2-8d12-05dc0b68e732

Details from Kashav:

iirc, it's testing that we process switch correctly when we POST from a file uri
and that we process switch when we have browser.tabs.remote.useHTTPResponseProcessSelection enabled and don't when it's disabled
(the test_disabled is irrelevant when fission is enabled)

zombie, with the dependency DocumentChannel bug is now resolved, what's left to do for this to unblock Kashav for bug 1596217?

Looking into.

This doesn't seem to reproduce anymore, at least on Windows, both opt and debug with --verify.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=2dcbde23aa7874091f648326d888d381da7a3e14

On Linux, I'm still seeing the error, but the test no longer hangs. We skip (ignore?) 15 tests when Fission is enabled ("Ran 23 checks (22 subtests, 1 tests)" with Fission and "Ran 38 checks (37 subtests, 1 tests)" without Fission).

(also looks like the test was renamed to browser_documentChannel.js in bug 1592894 (https://phabricator.services.mozilla.com/D55793)).

(In reply to :kashav from comment #8)

We skip (ignore?) 15 tests when Fission is enabled

Details from Kashav:

(the test_disabled is irrelevant when fission is enabled)

Oops.

I still see the error message though, guess it was unrelated to the test (why would it have been hanging there?). Not sure if it's something we still need to fix.

The error message is unrelated and will be fixed in a different bug. Updating summary and component to reflect this.

The product::component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.

The patch to unskip this test has landed in bug 1592894.