Currently, we build android emulator packages manually and upload to
tooltool.
This patch switches it to be pulled from the toolchain built artifacts.
This also allows android tests to run in the staging environment.
Differential Revision: https://phabricator.services.mozilla.com/D68617
--HG--
extra : moz-landing-system : lando
Use finer granularity for some reftest/mochitest SCHEDULES.exclusive entries,
so that reftest-plain does not run when only crashtests are modified, and
vice versa; similarly, break up mochitest into mochitest/browser-chrome/chrome/
a11y. Use schedules-component instead of category.
Differential Revision: https://phabricator.services.mozilla.com/D60085
--HG--
extra : moz-landing-system : lando
Changes:
Remove all tests other than `reftests`, `crashtests` and `mochitest-media` for windows10-aarch64.
Important changes are in `taskcluster/ci/test/test-platforms.yml` and `taskcluster/ci/test/test-sets.yml`.
I've gone ahead and removed the windows10-aarch64 specific entries in the YAML files as well.
Differential Revision: https://phabricator.services.mozilla.com/D65654
--HG--
extra : moz-landing-system : lando
Changes:
Update `linux64` regex to in yaml files for suites that have been migrated over to run on ubuntu1804.
Current naming convention: `linux64-asan/opt`.
New naming convention: `linux1804-64-asan/opt`
Future (potential) convention: `linux2004-64-asan/opt`
Using the `linux.*64` regex will result in a match for all three of the names above. This will ensure that we don't need to constantly update the regex for each new version, while being specific enough.
Differential Revision: https://phabricator.services.mozilla.com/D59572
--HG--
extra : moz-landing-system : lando
Stop running integration branch browsertime tasks on windows10-aarch64;
these were added recently in bugs 1585013 and bug 1604113 but I don't
think there was any specific consideration of windows10-aarch64.
Restore mochitest-media and all reftest tests on mozilla-central only
on windows10-aarch64.
Differential Revision: https://phabricator.services.mozilla.com/D57658
--HG--
extra : moz-landing-system : lando
This implements a 'fission-run-by-projects' and 'fission-tier' key that mirrors
the non-fission versions. We need to duplicate the keys rather than use
something like 'by-variant' due to the order that things are processed in the
tests.py transforms.
These keys should only be temporary until Fission is running the same as
non-Fission. In the meantime they will give us greater control over what runs
where.
The taskgraph generated before and after this change is identical.
Differential Revision: https://phabricator.services.mozilla.com/D56211
--HG--
extra : moz-landing-system : lando
In bug 1596368 we will adjust them, after disabling tests in coverage debug builds.
Depends on D53000
Differential Revision: https://phabricator.services.mozilla.com/D53001
--HG--
extra : moz-landing-system : lando
Change the taskcluster max-run-time for mochitests and reftests to use the
defaults, now that android tests no longer run anywhere near 7200 seconds.
(Also noticed some unrelated tc configuration that is obsolete - tidied that.)
Also remove the special 600 second reftest timeout for android debug reftests.
Differential Revision: https://phabricator.services.mozilla.com/D47301
--HG--
extra : moz-landing-system : lando
Stop running all Fennec functional (non-performance) tests:
- stop running all Android 4.3 tests
- switch android-em-7 cppunit and android-hw jittest from the Fennec apk to the
geckoview apk (no difference in behavior expected)
- stop running Android 7.0 marionette tests, since they also run against Fennec
- remove android-em-4.* references from taskcluster configs
- remove android instance: extra-large references from taskcluster configs,
since they only affect aws, which is no longer used for Android
Android-hw raptor tests running against Fennec remain; I will prepare a separate
patch for those.
Differential Revision: https://phabricator.services.mozilla.com/D43684
--HG--
extra : moz-landing-system : lando
This uses the layers.d3d11.enable-blacklist pref to allow running WebRender on WARP.
Differential Revision: https://phabricator.services.mozilla.com/D42255
--HG--
extra : moz-landing-system : lando
This uses the layers.d3d11.enable-blacklist pref to allow running WebRender on WARP.
Differential Revision: https://phabricator.services.mozilla.com/D42255
--HG--
extra : moz-landing-system : lando
This uses the layers.d3d11.enable-blacklist pref to allow running WebRender on WARP.
Differential Revision: https://phabricator.services.mozilla.com/D42255
--HG--
extra : moz-landing-system : lando
This uses the layers.d3d11.enable-blacklist pref to allow running WebRender on WARP.
Differential Revision: https://phabricator.services.mozilla.com/D42255
--HG--
extra : moz-landing-system : lando
Switch android-hw jsreftest to geckoview. Technically this runs all
android-hw reftests on geckoview -- I don't imagine we'll ever want to
run any android-hw fennec reftests.
Differential Revision: https://phabricator.services.mozilla.com/D39350
--HG--
extra : moz-landing-system : lando
As far as I can tell, the intermittent suite_start failures are due to
stdout/stderr output interleaving -- a known issue for reftest logging,
without a clear way forward. Let's work around it the same way we did
on Windows.
Differential Revision: https://phabricator.services.mozilla.com/D37023
--HG--
extra : moz-landing-system : lando
Only enabled on try/m-c as tier-2 for now, per email discussion, to minimize
load on bitbar Pixel 2 devices.
Depends on D36799
Differential Revision: https://phabricator.services.mozilla.com/D36800
--HG--
extra : moz-landing-system : lando
Only enabled on try/m-c as tier-2 for now, per email discussion, to minimize
load on bitbar Pixel 2 devices.
Depends on D36799
Differential Revision: https://phabricator.services.mozilla.com/D36800
--HG--
extra : moz-landing-system : lando
These changes are needed for consistently green runs with the new emulator with
"-gpu on".
Most changes are simple removal of fuzzy-if(geckoview) but I also needed to add
at least one new fuzzy-if.
In this configuration we can run reftests in just 2 chunks (20 minutes each on
opt/30 minutes on debug).
Differential Revision: https://phabricator.services.mozilla.com/D36258
--HG--
extra : moz-landing-system : lando
Tests are imported from test262 upstream so this test suite is expected to become slower over time.
Differential Revision: https://phabricator.services.mozilla.com/D36295
--HG--
extra : moz-landing-system : lando
Changes:
- migrate jsreftest over to macosx1014
- re-balance the chunks for non-ccov variants of macosx1014
Differential Revision: https://phabricator.services.mozilla.com/D34771
--HG--
extra : moz-landing-system : lando
These tasks normally run in 45 to 55 minutes; if they exceed 60 minutes, the
task fails. Failures are not frequent, but I would like to avoid them. We could
increase chunks, but it looks like we have handled the other ccov cases like
this, by increasing the max-run-time.
Differential Revision: https://phabricator.services.mozilla.com/D33656
--HG--
extra : moz-landing-system : lando
Incremental effort to improve android-hw device availability: Stop running android-hw
debug jsreftest and jittest on integration branches.
Also, remove the option for android-hw opt jittest on try. opt is a nice alternative
to pgo on try in general, but the risk of accidental (unnecessary) inclusion in
try pushes makes this a luxury we cannot afford on android-hw.
Differential Revision: https://phabricator.services.mozilla.com/D33156
--HG--
extra : moz-landing-system : lando
Changes:
- add `jsreftest` to the list of permitted tests to run on `android-hw-p2-8-0-arm7-api-16`
- add necessary mozharness setup for `android-hw` for jsreftest
- disable `android-em` from running jsreftests
Differential Revision: https://phabricator.services.mozilla.com/D32262
--HG--
extra : moz-landing-system : lando