There is a duplicate setting for a pref in raptor's user.js file. This patch removes the duplicate.
Differential Revision: https://phabricator.services.mozilla.com/D48204
--HG--
extra : moz-landing-system : lando
This patch adds fullscreen and windowed youtube tests for the V9 and H264 encoding at 1080p30 and 1080p60. Each subtest runs for 20 page cycles which amounts to about 5 minutes each. It also begins adding these to power test tasks running on the macosx-1014 reference hardware.
Differential Revision: https://phabricator.services.mozilla.com/D45067
--HG--
extra : moz-landing-system : lando
This pref is required by the common animation interpolation test function used
in many of the CSS test suites but currently we only enable it on Nightly. As a
result, each time a new spec adds animation tests, we get failures on our beta
simulations. Rather than turn this on for each directory it is used in each
time a new failure occurs, this patch makes us set it globally.
This patch also removes a number of instances where we set this pref locally.
It only removes the instances that were specifically added due to the
introduction of the common CSS interpolation test function. The existing
instances remain untouched since they serve as documentation of other places
where we are specifically testing that feature.
Differential Revision: https://phabricator.services.mozilla.com/D47034
--HG--
extra : moz-landing-system : lando
Add new preference `extensions.webextensions.warnings-as-errors` that
defaults to `true` in tests. Tests that expect warnings are modified
to briefly flip the pref for the specific part of the test that needs
an exception.
As part of the refactor, log entries for schema entries that contain
`"onError": "warn"` will now be prefixed by "Warning" instead of
"Error", to be consistent with the change from bug 1495908.
Differential Revision: https://phabricator.services.mozilla.com/D40548
--HG--
extra : moz-landing-system : lando
Add new preference `extensions.webextensions.warnings-as-errors` that
defaults to `true` in tests. Tests that expect warnings are modified
to briefly flip the pref for the specific part of the test that needs
an exception.
As part of the refactor, log entries forschema entries that contain
`"onError": "warn"` will now be prefixed by "Warning" instead of
"Error", to be consistent with the change from bug 1495908.
Differential Revision: https://phabricator.services.mozilla.com/D40548
--HG--
extra : moz-landing-system : lando
Hooks up slow script reporting to the ContentDelegate. Allowing slow script prompts to be implemented.
Differential Revision: https://phabricator.services.mozilla.com/D41970
--HG--
extra : moz-landing-system : lando
My previous attempt updated the wrong test profile, which does not apply to xpcshell tests.
This applies the pref override to xpcshell tests only, the only place we need it.
Differential Revision: https://phabricator.services.mozilla.com/D42865
--HG--
extra : moz-landing-system : lando
Also, remove an old obsolete preference (getWithPerformance) from test profiles.
Differential Revision: https://phabricator.services.mozilla.com/D40623
--HG--
extra : moz-landing-system : lando
This pref defaults to true, but geckoview builds set it to false. Several tests assume
this pref is set; some android xpcshell tests currently fail when run against the geckoview apk
for this reason. Setting the pref in the test profile means that geckoview tests will run
with a different pref value than geckoview would normally use, but aligns the geckoview
test environment with firefox. (An alternative would be to skip geckoview tests that rely
on the pref.)
Differential Revision: https://phabricator.services.mozilla.com/D38585
--HG--
extra : moz-landing-system : lando
This provides a set of promises that the searchservice resolves once the search engine has been configured
Differential Revision: https://phabricator.services.mozilla.com/D33660
--HG--
extra : moz-landing-system : lando
This provides a set of promises that the searchservice resolves once the search engine has been configured
Differential Revision: https://phabricator.services.mozilla.com/D33660
--HG--
extra : moz-landing-system : lando
This provides a set of promises that the searchservice resolves once the search engine has been configured
Differential Revision: https://phabricator.services.mozilla.com/D33660
--HG--
extra : moz-landing-system : lando
(The pref is about to be removed, but even before its removal, it defaults to
'true' so these tests don't need to bother setting/checking it.)
Differential Revision: https://phabricator.services.mozilla.com/D33805
--HG--
extra : moz-landing-system : lando
Sometime wpt runs test even before the document becomes visible, which would delay `video.play()` and cause `play()` running in wrong order.
Differential Revision: https://phabricator.services.mozilla.com/D32079
--HG--
extra : moz-landing-system : lando
Sometime wpt runs test even before the document becomes visible, which would delay `video.play()` and cause `play()` running in wrong order.
Differential Revision: https://phabricator.services.mozilla.com/D32079
--HG--
extra : moz-landing-system : lando
Sometime wpt runs test even before the document becomes visible, which would delay `video.play()` and cause `play()` running in wrong order.
Differential Revision: https://phabricator.services.mozilla.com/D32079
--HG--
extra : moz-landing-system : lando
The Content Security Policy tests were handling the smaller android preload
values that were #defined on Android by setting media.preload.default=2. Now
that we're detecting whether we're on cellular or not, and the android
emulators that our tests run on emulate a cellular connection, just setting
media.preload.default is no longer enough.
So set media.preload.default.cellular=2 in the CSP mochitests instead of
media.preload.default, to make the CSP mochitests pass in the Android
emulators.
Differential Revision: https://phabricator.services.mozilla.com/D29617
--HG--
extra : moz-landing-system : lando
The Content Security Policy tests were handling the smaller android preload
values that were #defined on Android by setting media.preload.default=2. Now
that we're detecting whether we're on cellular or not, and the android
emulators that our tests run on emulate a cellular connection, just setting
media.preload.default is no longer enough.
So set media.preload.default.cellular=2 in the CSP mochitests instead of
media.preload.default, to make the CSP mochitests pass in the Android
emulators.
Differential Revision: https://phabricator.services.mozilla.com/D29617
--HG--
extra : moz-landing-system : lando