In bug 1732358 we will be switching the default value for `fission.autostart` to True, sometime in the Nightly 96 cycle (which starts next week). Once this happens, any test harness that isn't explicitly turning fission off will magically start running with fission. This means that: 1. We'll lose non-fission test coverage 2. Task labels will be wrong (as well as consumers that depend on them) Before this switch happens, we should make sure that all of our test harnesses either explicitly enable or disable fission so that flipping the pref has no effect on our CI or test coverage.
Bug 1736859 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
In bug 1732358 we will be switching the default value for `fission.autostart` to True, sometime in the Nightly 96 cycle (which starts Nov 1st). Once this happens, any test harness that isn't explicitly turning fission off will magically start running with fission. This means that: 1. We'll lose non-fission test coverage 2. Task labels will be wrong (as well as consumers that depend on them) Before this switch happens, we should make sure that all of our test harnesses either explicitly enable or disable fission so that flipping the pref has no effect on our CI or test coverage.