Enable Interventions in Nightly
Categories
(Firefox :: Address Bar, task, P2)
Tracking
()
| 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.
| Reporter | ||
Comment 1•5 years ago
|
||
Try run on top of bug 1613603 with Interventions enabled: https://treeherder.mozilla.org/#/jobs?repo=try&revision=2e0d2faad707fd18216737a50922d1d151fefb4e
| Reporter | ||
Updated•5 years ago
|
| Reporter | ||
Comment 2•5 years ago
|
||
Comment 4•5 years ago
|
||
Backed out changeset d619690c640b (bug 1613608) for xpcshell failures in test_UrlbarQueryContext_restrictSource.js
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=287745991&repo=autoland&lineNumber=4713
and https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=287748880&repo=autoland&lineNumber=2305
Backout: https://hg.mozilla.org/integration/autoland/rev/014b0d94c202656bc3394e46780c0c1fcf9d031a
| Reporter | ||
Comment 5•5 years ago
|
||
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
| Assignee | ||
Comment 6•5 years ago
|
||
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.
| Assignee | ||
Comment 7•5 years ago
|
||
| Assignee | ||
Comment 8•5 years ago
|
||
The patch I just posted fixes it for me locally, and the main interventions test still passes.
| Reporter | ||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 10•5 years ago
|
||
| bugherder | ||
Description
•