This patch changes how Google Chrome for Android is deployed. Rather than relying on automatic updates, we will use tooltool to download the APK and install it ourselves. Some changes were done in taskcluster to remove a hack that was put in place to disable interal tooltool downloads (the issue is resolved now).
A tooltool manifest is added for this, and to keep ourselves organized, all manifests (including the playback ones) are moved into a folder called `tooltool-manifests`.
Differential Revision: https://phabricator.services.mozilla.com/D72198
Split out jsreftest and jittest files into their own packages, removing them
from the common package.
This speeds up extracting files from the common test archive for
non-jsreftest/jittest suites.
Also, remove some files from the web-platform test archive that are already
present in the common archive.
Differential Revision: https://phabricator.services.mozilla.com/D72192
This is the first patch of a multi-part patch to enable live site testing on Google Chrome for Android and Fenix. It adds the `--live-sites` command line option that disables the mozproxy playback (or enables live sites) when it is supplied.
Differential Revision: https://phabricator.services.mozilla.com/D69051
Browsertime's -vvv displays the gecko profile passed through HTTP
in the logs, making them very big. This patch makes verbose output
an option and deactivates it by default.
Differential Revision: https://phabricator.services.mozilla.com/D71511
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
This patches fixes several problems found on Raptor and the condprof:
Raptor:
- Make sure the conditioned profile dir is removed after
it's been used, not before.
- Adds the --project option to raptor so we know if we're on try
autoland or mozilla-central.
- Both Fennec and Fenix are deactivated for now
- Use the allow-downgrade flag to be flexible on build ids (the next step will be bug 1628666)
Conditioned profiles, curation of the profile prefs:
- Fully deactivates Normandy during Raptor tests (app.normandy.enabled)
- Removes any GFX blacklisting (gfx.blacklist.*)
- Removes any marionette pref
- Enforce extensions sideloading (extensions.startupScanScopes)
Differential Revision: https://phabricator.services.mozilla.com/D70518
Activates the conditioned profile by doing the following changes:
- make sure the conditioned profile dir is removed after
it's been used, not before.
- add the --project option to raptor so we know if we're on try
or mozilla-central.
- Both Fennec and Fenix are deactivated for now.
- Remove any gfx.blacklist.* prefs when using a conditioned profile
Differential Revision: https://phabricator.services.mozilla.com/D70518
--HG--
extra : moz-landing-system : lando
Make sure the conditioned profile dir is removed after
it's been used, not before. This patch also adds the
--project option to raptor so we know if we're on try
or mozilla-central. Both Fennec and Fenix are deactivated
for now.
Differential Revision: https://phabricator.services.mozilla.com/D70518
--HG--
extra : moz-landing-system : lando
This runs wpt with --processes=2 in CI, excluding wdspec tests where this
causes obvious test failures and android where we can't have more than a
single instance. This should provide some speedup at the cost of possibly
increased instability. So following landing this it will be necessary to
look out for an increased rate of intermittents.
Differential Revision: https://phabricator.services.mozilla.com/D68885
--HG--
extra : moz-landing-system : lando
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
The definition for reftest/crashtest variants of web-platform-tests in web-platform.yml has a trailing `s` which is technically incorrect.
This causes problems when querying ActiveData for the runtimes for these subsuites since the suite name recorded in ActiveData has the trailing s.
Changes:
- remove the trailing `s` from the definitions
Differential Revision: https://phabricator.services.mozilla.com/D68069
--HG--
extra : moz-landing-system : lando
This runs wpt with --processes=2 in CI, excluding wdspec tests where this
causes obvious test failures and android where we can't have more than a
single instance. This should provide some speedup at the cost of possibly
increased instability. So following landing this it will be necessary to
look out for an increased rate of intermittents.
Differential Revision: https://phabricator.services.mozilla.com/D68885
--HG--
extra : moz-landing-system : lando
This patch adds the capability to run Google Chrome for Android tests through Raptor-Browsertime.
Chrome must be available on the device being tested, and there are no installation steps being added in this patch since CI already has the latest Chrome version available to test with. That said, this patch adds the ability to find the version of Chrome that is being tested and stores this in the Perfherder artifact. Getting this version is also necessary to be able to run Chrome with the correct chromedriver.
Two tests are initially be enabled for Chrome in this patch: Amazon, and YouTube. They will only run through a cron task three days a week. The other changes done in this patch are required for Chrome to work with Raptor-Browsertime.
Differential Revision: https://phabricator.services.mozilla.com/D65610
--HG--
extra : moz-landing-system : lando
This converts `--setenv` into `env` in `try_task_config` at parameter
generation time.
Differential Revision: https://phabricator.services.mozilla.com/D66537
--HG--
extra : moz-landing-system : lando
Before Bug 1530908, the build script used `TryToolsMixin.try_message_has_flag`
to dectect a request for artifact builds. Since that is no longer used, we can
remove the dependency.
Differential Revision: https://phabricator.services.mozilla.com/D65842
--HG--
extra : moz-landing-system : lando
The taskcluster decision task makes an imperfect decision about when to run test-verify, so
test-verify tasks sometimes find they have no tests to run and bail out early. The existing
bail-out is problematic for ETL ingestion, which expects to see start/finish for each
mozharness step. This patch removes the fatal bail-out (warns instead) allowing all the
mozharness steps to complete; since there's no work to do, steps generally complete quickly.
(I noticed another early return from the same function, for the missing repo/rev case and
updated that as well, for consistency; note that no callers use the function return value.)
Differential Revision: https://phabricator.services.mozilla.com/D66062
--HG--
extra : moz-landing-system : lando
This patch removes a `storage.local.clear()` call from raptor-webext for causing a high number of intermittent failures. It also adds a default value for `--host` in the mozharness raptor. Finally, a delayed startup for raptorRunner is added with the hope that this will further decrease intermittents (right now, it might be starting at a very noisy time).
Differential Revision: https://phabricator.services.mozilla.com/D65893
--HG--
extra : moz-landing-system : lando
We don't ship openh264 builds on android, so there is no need
to build them in automation.
Differential Revision: https://phabricator.services.mozilla.com/D65669
--HG--
extra : moz-landing-system : lando
This is instead of extracting them in the gecko source directory, where they
will get deleted by the next task anyway.
Differential Revision: https://phabricator.services.mozilla.com/D65628
--HG--
extra : moz-landing-system : lando
This moves the object directory and source directories around in all mozharness
jobs, to allow enabling caching on windows builders.
This makes a number of changes that all need to land at once:
- Move the source checkout for the workspace cache mount, to the checkouts
cache mount.
- Makes the object directoy from underneath the source directory, to directly
in the work directory (which is still under `workspace`).
- Sets the object directory to `obj-build` instead of `obj-firefox`.
- Stops caching the workspace directory (it is still a volume in docker workers,
so writes perform well; a followup revision add some checks around this).
- Removes one level of directory in the mozharness workdir (things were under
`workspace/build`, but are now just under `workspace/`.
- Adjust paths in environment variables and artifact specifications to match
the above changes.
Differential Revision: https://phabricator.services.mozilla.com/D62482
--HG--
extra : moz-landing-system : lando
Gregory Mierzwinski
Joel Maher
Chris AtLee
Bob Clary
Bogdan Tara
Tarek Ziadé
Andreea Pavel
Wander Lairson Costa
Myeongjun Go
Edwin Takahashi
Mihai Alexandru Michis
Csoregi Natalia
James Graham
Noemi Erli
Ricky Stewart
Mike Hommey
Stefan Hindli
Bastien Abadie
Ciure Andrei
Tom Prince
Sylvestre Ledru
Ben Hearsum
Geoff Brown