This helper only has 2 callers. Just use BrowserTestUtils.waitForContentEvent
directly.
Depends on D51441
Differential Revision: https://phabricator.services.mozilla.com/D52058
--HG--
extra : moz-landing-system : lando
This also changes BrowserTestUtils.addContentEventListener to use browsing
contexts to track added listeners and their associated targets.
Depends on D52105
Differential Revision: https://phabricator.services.mozilla.com/D51441
--HG--
extra : moz-landing-system : lando
These are thrown when the actor no longer has a manager but attempts to access
its docshell or browsing context. We may arrive at this state without seeing
a willDestroy() if the process is being shutdown or the actor was destroyed from
the parent.
Depends on D51440
Differential Revision: https://phabricator.services.mozilla.com/D52105
--HG--
extra : moz-landing-system : lando
Various BrowserTestUtils.waitForContentEvent call sites expect to see an event
on a browser element that was open before the call was made. For this reason,
each of the browsers need to also have a ContentEventListener actor.
Depends on D51439
Differential Revision: https://phabricator.services.mozilla.com/D51440
--HG--
extra : moz-landing-system : lando
This also changes BrowserTestUtils.addContentEventListener to use browsing
contexts to track added listeners and their associated targets.
Differential Revision: https://phabricator.services.mozilla.com/D51441
--HG--
extra : moz-landing-system : lando
Various BrowserTestUtils.waitForContentEvent call sites expect to see an event
on a browser element that was open before the call was made. For this reason,
each of the browsers need to also have a ContentEventListener actor.
Differential Revision: https://phabricator.services.mozilla.com/D51440
--HG--
extra : moz-landing-system : lando
This also changes BrowserTestUtils.addContentEventListener to use browsing
contexts to track added listeners and their associated targets.
Differential Revision: https://phabricator.services.mozilla.com/D51441
--HG--
extra : moz-landing-system : lando
Various BrowserTestUtils.waitForContentEvent call sites expect to see an event
on a browser element that was open before the call was made. For this reason,
each of the browsers need to also have a ContentEventListener actor.
Differential Revision: https://phabricator.services.mozilla.com/D51440
--HG--
extra : moz-landing-system : lando
This patch updates ssltunnel to enable TLS session tickets. With the NSS change to update the TLS version default to 1.3 (where it was 1.2 prior), this is necessary to support resumption.
Differential Revision: https://phabricator.services.mozilla.com/D51129
--HG--
extra : moz-landing-system : lando
The current implementation of addContentEventListener() is centered
around the message manager. When any message manager goes away, it
cleans up everything, which does not work when Fission is enabled and
we do a cross-process navigation.
My new implementation instead uses window actors. Message manager
shared state is used to store the set of expected event listeners. New
windows, after the function is called for the first time in a test,
will get listeners added properly. Of windows that exist at the first
time the function is called in a test, only windows associated with
the BC of the browser that is passed in will get added, which is a
disadvantage relative to the current setup. That could probably be
fixed.
We auto remove at the end of the test, not when any message manager is
torn down, so there's never a need to disable auto removal.
Differential Revision: https://phabricator.services.mozilla.com/D48777
--HG--
extra : moz-landing-system : lando
This allows generic code, like a testing JSM, to do clean up when a
test completes, in a way that will work in different test suites.
Differential Revision: https://phabricator.services.mozilla.com/D50648
--HG--
extra : moz-landing-system : lando
Adds an additional "unload" listener in BrowserTestUtils.browserLoaded to
unregister the original load listener and reject the promise.
This was broken because BrowserTestUtils.waitForNewWindow adds an observer that
fires for every new window. The observer calls BrowserTestUtils.browserLoaded on
all of these windows, and since only one of them loads the URL we care about, we
never unregister the event listeners from the remaining windows.
Depends on D49005
Differential Revision: https://phabricator.services.mozilla.com/D50658
--HG--
extra : moz-landing-system : lando
This also updates the two functions (BrowserTestUtils.firstBrowserLoaded,
browser_broadcastchannel.js#browserFrameLoaded) that rely on the previous
event to use the new one.
Depends on D49001
Differential Revision: https://phabricator.services.mozilla.com/D49002
--HG--
extra : moz-landing-system : lando
Bug 1267643 removed filtering of client certificates based on the
"certificate_authorities" list sent in the client certificate request from the
server in TLS handshakes because it is impossible to implement as specified
without false negatives (i.e. excluding certificates that could be usable but
don't seem to be according to the certificates the client is aware of). In
practice, however, it seems enough users rely on this behavior[0] that we
should add it back until the platform can save client certificate selections
across restarts and the "select one automatically" option is removed (see also
bug 634697).
[0] See e.g. bug 1588703, bug 1590297, bug 1590596, bug 1074195 comment 27,
and any other duplicates of this bug.
Differential Revision: https://phabricator.services.mozilla.com/D50355
--HG--
extra : moz-landing-system : lando
Added a loop for repeating the requested test(s).
With --run-until-failure, loop until a test fails.
With --repeat=N, repeat N times. eg, --repeat=1 implies 2 runs total (same as mochitest).
(Incidentally moved code for --enable-webrender since it was not in the appropriate section.)
Differential Revision: https://phabricator.services.mozilla.com/D50299
--HG--
extra : moz-landing-system : lando
This also updates the two functions (BrowserTestUtils.firstBrowserLoaded,
browser_broadcastchannel.js#browserFrameLoaded) that rely on the previous
event to use the new one.
Differential Revision: https://phabricator.services.mozilla.com/D49002
--HG--
extra : moz-landing-system : lando
All but browser_bug744745.js seem to pass even without the fixes I
made, which seems odd.
browser_bug1058164.js is a little odd because it passes in {} instead
of a boolean for the useCapture argument. I think this ends up calling
addEventListener(..., {}, false), which should be the equivalent of
addEventListener(..., {}).
Differential Revision: https://phabricator.services.mozilla.com/D49453
--HG--
extra : moz-landing-system : lando
Most of these tests have been disabled for a long time; they run well
in the current test environment.
With the additional tests running, task times increase; I have added one
more test chunk for android mochitest-plain.
These tests were identified from a random sampling of mochitest manifests;
I intend to enable more mochitests in future patches.
Differential Revision: https://phabricator.services.mozilla.com/D48912
--HG--
extra : moz-landing-system : lando
This leaves the testharness files, because they are used in various mochitests.
Differential Revision: https://phabricator.services.mozilla.com/D49132
--HG--
extra : moz-landing-system : lando
This leaves the testharness files, because they are used in mochitest-chrome
tests in dom/animation/test.
Differential Revision: https://phabricator.services.mozilla.com/D49132
--HG--
extra : moz-landing-system : lando
This leaves the testharness files, because they are used in mochitest-chrome
tests in dom/animation/test.
Differential Revision: https://phabricator.services.mozilla.com/D49132
--HG--
extra : moz-landing-system : lando
Due to limitations in the test harness, the "serviceworker_e10s" (for mochitest
and xpcshell) and "sw-e10s" (for WPT) values will match mozinfo's "nightly_build"
value, unless overridden by "--setpref dom.serviceWorkers.parent_intercept=..."
provided at the CLI.
Differential Revision: https://phabricator.services.mozilla.com/D43170
--HG--
extra : moz-landing-system : lando
Due to limitations in the test harness, the "serviceworker_e10s" (for mochitest
and xpcshell) and "sw-e10s" (for WPT) values will match mozinfo's "nightly_build"
value, unless overridden by "--setpref dom.serviceWorkers.parent_intercept=..."
provided at the CLI.
Differential Revision: https://phabricator.services.mozilla.com/D43170
--HG--
extra : moz-landing-system : lando
mochitest-chrome is not supported with geckoview and attempts to run chrome
tests with geckoview result in a hang. mach test runs can accidentally attempt
to run chrome tests if the flavor is not specified and the directory contains
a chrome.ini manifest.
Existing harness support allows for filtering flavors based on buildapp, like
android, but not by run-time app like geckoview, so this patch disables
mochitest-chrome for all android runs.
Differential Revision: https://phabricator.services.mozilla.com/D47943
--HG--
extra : moz-landing-system : lando
Removes all the robocop test files and most robocop support. @RobocopTarget annotations and some build configuration is intentionally left untouched at this time, in case there is additional risk involved; a good task for follow-up.
Differential Revision: https://phabricator.services.mozilla.com/D45671
--HG--
extra : moz-landing-system : lando
Kashav Madan
Dorel Luca
Brindusan Cristian
Anny Gakhokidze
Kevin Jacobs
Gijs Kruitbosch
Andrew McCreight
Neil Deakin
Dana Keeler
Gurzau Raul
Geoff Brown
Geoff Lankow
Christian Holler
Brian Grinstead
Ms2ger
shindli
Andrew Halberstadt
Kris Maglione
Johann Hofmann
Perry Jiang
Daniel Varga
Nika Layzell
Christoph Kerschbaumer
Matthew Noorenberghe