test_fission_autostart.py being accidentally skipped in all configurations
Categories
(Core :: DOM: Content Processes, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox95 | --- | wontfix |
firefox96 | --- | wontfix |
firefox97 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fission])
The test_fission_autostart.py
test is configured to automatically pass with a success on platforms where the initial preference state isn't configured to be the default. It appears that at some point when preparing for enabling fission by default, we explicitly used a user preference to disable fission.autostart
in all configurations, and caused the check in https://searchfox.org/mozilla-central/rev/6a7c3a1eda4ebb8f9c13779dbbf5eff15bacf8ed/toolkit/xre/test/marionette/test_fission_autostart.py#89-92 to always return True
, skipping all of the tests.
Simply removing the check will not work, as having the pref as required prevents us from changing it's value throughout the test, breaking it.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Thanks for noticing this, the pref started being explicitly set here:
https://hg.mozilla.org/integration/autoland/rev/edd0ea14fcca
I'm not too clear on the intent of these tests, so redirecting to whimboo who hopefully has some ideas.
Comment 2•3 years ago
|
||
I reviewed a patch for that from Nika some days ago. I assume the wrong bug number was referenced in the commit message so that it doesn't appear on this bug?
Assignee | ||
Comment 3•3 years ago
|
||
Yes, I am fixing this in part 1 of bug 1732358
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Set release status flags based on info from the regressing bug 1736859
Comment 5•3 years ago
|
||
Assigning to Nika because she is fixing this in bug 1732358 part 1.
We won't need to uplift this test fix to Beta 96.
Updated•3 years ago
|
Updated•3 years ago
|
Comment 6•3 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #5)
Assigning to Nika because she is fixing this in bug 1732358 part 1.
I'm a bit confused. What's left in this bug after bug 1732358 is landed?
We won't need to uplift this test fix to Beta 96.
Updated•3 years ago
|
Assignee | ||
Comment 7•3 years ago
|
||
Fixed by bug 1732358
Updated•3 years ago
|
Description
•