Look into fission extraOption issues on Fenix
Categories
(Testing :: Raptor, defect, P1)
Tracking
(firefox-esr91 unaffected, firefox100 unaffected, firefox101 unaffected, firefox102 unaffected, firefox103 fixed)
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox100 | --- | unaffected |
| firefox101 | --- | unaffected |
| firefox102 | --- | unaffected |
| firefox103 | --- | fixed |
People
(Reporter: sparky, Assigned: sparky)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Fission was turned on by bug 1762991 for mobile tests. We need to disable this immediately.
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
|
||
(In reply to Greg Mierzwinski [:sparky] from comment #0)
Fission was turned on by bug 1762991 for mobile tests. We need to disable this immediately.
This is unclear (it looks like it was on for a while but no option was being added), I'm looking into it further.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
Set release status flags based on info from the regressing bug 1762991
| Assignee | ||
Comment 3•3 years ago
|
||
So fission was definitely turned on in all mobile tests across mozilla-central, autoland, and fenix with that patch. The reason it was confusing is that there is now an entry called "fission" in the config but it's not being used properly. I'm working on a patch now.
| Assignee | ||
Comment 4•3 years ago
|
||
This patch adds a hack to prevent fission from being enabled on mobile unless the pref was explicitly passed through a command-line option.
Updated•3 years ago
|
Comment 5•3 years ago
|
||
Greg, you set that bug as P1/S1 and requested tracking, is that a release blocker? Is that something that will prevent us from building Fenix and Focus beta today? It is also unclear to me why you requested tracking tor 101 as the regressor landed in 102 and the patch wasn't uplifted. Thanks.
| Assignee | ||
Comment 6•3 years ago
|
||
(In reply to Pascal Chevrel:pascalc from comment #5)
Greg, you set that bug as P1/S1 and requested tracking, is that a release blocker? Is that something that will prevent us from building Fenix and Focus beta today? It is also unclear to me why you requested tracking tor 101 as the regressor landed in 102 and the patch wasn't uplifted. Thanks.
Hi :pascalc, sorry about that, I'm not sure how I requested tracking but it's not needed for this bug. I think it was the release management bot that may have triggered that so I've changed those settings.
Comment 8•3 years ago
|
||
| bugherder | ||
Description
•