Closed Bug 1613608 Opened 5 years ago Closed 5 years ago

Enable Interventions in Nightly

Categories

(Firefox :: Address Bar, task, P2)

task
Points:
2

Tracking

()

RESOLVED FIXED
Firefox 74
Iteration:
74.2 - Jan 20 - Feb 09
Tracking Status
firefox74 --- fixed

People

(Reporter: bugzilla, Assigned: adw)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

+++ This bug was initially created as a clone of Bug #1606910 +++

Product gave us the okay to enable Interventions in Nightly.

Assignee: nobody → htwyford
Status: NEW → ASSIGNED
Iteration: --- → 74.2 - Jan 20 - Feb 09

Drew, do you know what's happening here? This is related to the work in bug 1606918. The failure logs aren't very helpful, but running the tests locally it seems to be that the unit tests can't perform the update check because the XPCOM getter on the updateManager doesn't work. Here are the first few frames from a local failure:

Unexpected Results
------------------
FAIL browser/components/urlbar/tests/unit/test_UrlbarQueryContext_restrictSource.js - xpcshell return code: 0
ERROR Unexpected exception NS_ERROR_XPC_GS_RETURNED_FAILURE: ServiceManager::GetService returned failure code:
XPCU_serviceLambda@resource://gre/modules/XPCOMUtils.jsm:215:30
get@resource://gre/modules/XPCOMUtils.jsm:129:51
get isPending@resource:///modules/AppUpdater.jsm:107:1
get isReadyForRestart@resource:///modules/AppUpdater.jsm:157:5
check@resource:///modules/AppUpdater.jsm:66:9
checkForBrowserUpdate@resource:///modules/UrlbarProviderInterventions.jsm:641:18
isActive@resource:///modules/UrlbarProviderInterventions.jsm:504:10
start@resource:///modules/UrlbarProvidersManager.jsm:295:20
startQuery@resource:///modules/UrlbarProvidersManager.jsm:194:17
startQuery@resource:///modules/UrlbarController.jsm:133:24
get_results@/Users/harry/Developer/src/artifact/mozilla-central/objdir/_tests/xpcshell/browser/components/urlbar/tests/unit/test_UrlbarQueryContext_restrictSource.js:135:20
Flags: needinfo?(htwyford) → needinfo?(adw)

I'm not sure, but it's something like the update manager isn't available in an xpcshell environment. The toolkit/mozapps/update tests have xpcshell tests for different parts of update functionality, and there's a giant helper file they import so that they work. Presumably we would need to do the same to mock the update manager, but I'm only guessing. I don't think we should do that.

Can we do something like try-catch creating the manager and returning false from isActive if it failed? We don't need to test the interventions provider from xpcshell.

Flags: needinfo?(adw)

The patch I just posted fixes it for me locally, and the main interventions test still passes.

Assignee: htwyford → adw
Pushed by htwyford@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/61b059f65c1d Enable Interventions in Nightly but not in xpcshell tests. r=harry
Attachment #9124701 - Attachment is obsolete: true
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 74
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: