Follow-up to bug 2044390, which fixed the devtools tests that failed in the
try jobs run at the time. Standalone and all-mochitest jobs surface four more
tests in the same two failure classes.
browser_perf-02.js and browser_perf-04.js assert the profiler is inactive
before starting it. browser_perf-01.js already stops the startup profiler via
ProfilerTestUtils.assertProfilerInactive, and in a shared browser instance it
runs first and leaves the profiler stopped for the rest of the folder, hiding
these two. Standalone jobs restart the browser per test, so they each start
with the profiler active and fail; add the same add_setup call.
browser_toolbox_tabsswitch_shortcuts.js and the mozscreenshots
browser_devtools.js open the performance panel, whose
ProfilerEventHandling.componentWillUnmount issues a stopProfilerAndDiscardProfile
request on toolbox close that races the connection teardown and rejects (bug
2044383). Tolerate it with PromiseTestUtils.allowMatchingRejectionsGlobally,
like the four toolbox tests fixed in bug 2044390.
Differential Revision: https://phabricator.services.mozilla.com/D308218
Florian Quèze
e611cdb4b9