Closed Bug 1499363 Opened 7 years ago Closed 7 years ago

Perma X failures in xpcshell-remote.ini:toolkit/components/extensions/test/xpcshell/test_ext_userScripts.js when Gecko 64 merges to Beta on 2018-10-15

Categories

(WebExtensions :: General, defect)

defect
Not set
normal

Tracking

(firefox-esr60 unaffected, firefox62 unaffected, firefox63 unaffected, firefox64+ verified)

VERIFIED FIXED
mozilla64
Tracking Status
firefox-esr60 --- unaffected
firefox62 --- unaffected
firefox63 --- unaffected
firefox64 + verified

People

(Reporter: ebalazs_, Assigned: robwu)

References

Details

Attachments

(1 file)

Thanks for the report. The test failure is because this feature is disabled by default on non-Nightly. At the start of the test file, the preference is flipped to enable the feature. At the end of the test (before my new test), the runWithPrefs method is used to temporarily toggle the pref. This helper function does however not account for the original value; it simply clears the preference instead of pushing/popping the stack of overridden prefs. I intend to fix this by changing the the test and implementation of runWithPrefs to use SpecialPowers.pushPrefEnv and SpecialPowers.popPrefEnv instead of the current Services.prefs.setBoolPref + Services.prefs.clearUserPref.
Flags: needinfo?(rob)
Assignee: nobody → rob
Pushed by luca.greco@alcacoop.it: https://hg.mozilla.org/integration/autoland/rev/99d43f9d3918 Fix userScript test failure on beta due to runWithPrefs not restoring the initial prefs values. r=robwu
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: