`browser_Troubleshoot.js` fails when run locally because `nimbusRollouts` wasn't added to the schema when added
Categories
(Firefox :: Nimbus Desktop Client, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox98 | --- | wontfix |
| firefox99 | --- | fixed |
| firefox100 | --- | fixed |
People
(Reporter: Gijs, Assigned: beth)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
bug 1738286 added this property but didn't add it to the schema so now the test fails locally. I don't actually understand why this isn't orange on infra, and that might point to different brokenness.
An outside contributor noticed this (with some resulting confusion) in https://phabricator.services.mozilla.com/D140918.
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 1•4 years ago
|
||
Set release status flags based on info from the regressing bug 1738286
Comment 2•4 years ago
|
||
:andreio, since you are the author of the regressor, bug 1738286, could you take a look?
For more information, please visit auto_nag documentation.
Updated•4 years ago
|
| Assignee | ||
Updated•4 years ago
|
| Assignee | ||
Comment 3•4 years ago
|
||
I fired off a try run of just this test to see if it will fail: https://treeherder.mozilla.org/#/jobs?repo=try&revision=4278d5df8a85eaf93748b1097c5d1dc14d011e95
| Assignee | ||
Comment 4•4 years ago
|
||
This patch also fixes the test manifest to re-enable the test where appropriate.
Comment 6•4 years ago
|
||
| bugherder | ||
Comment 7•4 years ago
|
||
| bugherder uplift | ||
Description
•