Bug 1133260 - Disable browser_testOpenNewRemoteTabsFromNonRemoteBrowsers.js for non-e10s test runs. r=Mossop.

I don't think this test adds much value when it runs in non-e10s mode.
On top of that, because it relies on browser load events going over the
multiprocess add-on shims, this test will permafail when it goes onto
a channel with the shims disabled (like Aurora at the time of this writing).

So I'm disabling it for non-e10s test runs.
This commit is contained in:
Mike Conley 2015-02-17 17:29:07 -05:00
parent 25e1e25847
commit 8b8e05b4f1

View File

@ -429,7 +429,7 @@ skip-if = e10s
skip-if = e10s # Bug 1100664 - test relies on linkedBrowser.docShell skip-if = e10s # Bug 1100664 - test relies on linkedBrowser.docShell
[browser_tabs_owner.js] [browser_tabs_owner.js]
[browser_testOpenNewRemoteTabsFromNonRemoteBrowsers.js] [browser_testOpenNewRemoteTabsFromNonRemoteBrowsers.js]
skip-if = !e10s && os == "linux" # Bug 994541 - Need OMTC enabled by default on Linux, or else we get blocked by an alert dialog when opening e10s window. run-if = e10s
[browser_trackingUI.js] [browser_trackingUI.js]
support-files = support-files =
trackingPage.html trackingPage.html