This prevents the Mochitest browser-chrome tests under remote/ from
running in beta simulations, since the new Chromium-based remote
debugging protocol is only available on the Nightly release channel.
Differential Revision: https://phabricator.services.mozilla.com/D58504
--HG--
extra : moz-landing-system : lando
Avoid intermittent task timeouts by increasing the number of test chunks on the
affected platform.
Differential Revision: https://phabricator.services.mozilla.com/D58391
--HG--
extra : moz-landing-system : lando
Changes:
Remove `crashtest`, `mochitest-gpu` from running with ubuntu1604.
Add the above tests to run with ubuntu1804 image under `linux1804-64` label.
Remove `awsy` from linux64-qr/opt and linux64-shippable-qr/opt platforms.
Add `awsy` to linux1804-qr/opt and linux1804-shippable-qr/opt platforms.
Add new test set `linux180r-qr-tests` to serve as placeholder as `linux-qr-tests` are slowly migrated to the new test set.
Replace the usage of `linux1804-tests` for quantumrenderer platforms with the `linux-qr-tests` set.
Differential Revision: https://phabricator.services.mozilla.com/D58464
--HG--
extra : moz-landing-system : lando
Changes:
Remove `crashtest`, `mochitest-gpu`, `mochitest` and `xpcshelltest` from running with ubuntu1604.
Enable the above tests to run with ubuntu1804 image under `linux1804-64` label.
Differential Revision: https://phabricator.services.mozilla.com/D58464
--HG--
extra : moz-landing-system : lando
Changes:
Make available all variants of linux1804 for general use. Where appropriate, each variant is populated with `linux1804-tests`, which contain the shared tests that should run on all appropriate variants.
To deal with linux64-asan/opt and linux1804-64-asan/opt clashing in the taskgraph due to the translation service, remove `linux64/asan` entry from the translation dictionary and manually check in the `if/else` conditional later on.
Differential Revision: https://phabricator.services.mozilla.com/D58406
--HG--
extra : moz-landing-system : lando
Changes:
Change the python version used in mozharness testing to python3.6 as that's what the `linter` docker image has, not `python3.5`.
Promote the tier of mozharness-py3 test to tier 1 and run it on all repositories to ensure python3 compatibility for future changes.
Differential Revision: https://phabricator.services.mozilla.com/D58209
--HG--
extra : moz-landing-system : lando
This change introduces a "github-sync" component into tools,
which aims to support synchronizing both wgpu and WebRender with github.
~~It also features a "cargo test" job for standalone wgpu (bug 1596127)~~
The code is ported from "gfx/wr/scripts/wrupdater" folder. Changes are:
1. remove explicit WR parts and make them configurable by command line params
2. detect "mozilla-xxx" tags and use them in addition to the commits
As a follow up, wrupdater will be removed in favor of github-sync.
Status:
- [x] get the CI test job working
- [x] get @kats to fork "wgpu" github for "moz-gfx" bot
- [x] remove the wgpu testing CI job (into separate PR)
- [x] create new secret and reference it
Differential Revision: https://phabricator.services.mozilla.com/D57057
--HG--
extra : moz-landing-system : lando
When I was working on release-promotion for Thunderbird, I needed a way to
control the scriptworker worker-types used on try vs. on release branches.
At the time, there did not exist a way to vary worker types so I introduced
a scriptworker-specific way to vary the worker type.
Since then, we add support for worker aliases, which can currently vary by
level. This reuses that machinery for selecting signing workers.
Differential Revision: https://phabricator.services.mozilla.com/D58018
--HG--
extra : moz-landing-system : lando
Changes:
For existing `test-linux64` tasks, use the `linux-common-tests` list instead of `common-tests`. This is to permit striking off individual test suites from running on 1604 when the migration to 1804 is performed.
As a starting point, migrate `awsy` and `cppunit` to run on ubuntu1804 image under `test-linux1804-64` label.
- awsy is only for `opt` builds
- cppunit is for both `opt` and `debug` builds
Corresponding Treeherder pretty name PR is at https://github.com/mozilla/treeherder/pull/5788.
Differential Revision: https://phabricator.services.mozilla.com/D58204
--HG--
extra : moz-landing-system : lando
Some of these were busted in the initial push for wasm sandboxing; some
of these didn't break in that push, but seem likely to if/when we have
more complete coverage of turning on wasm sandboxing.
Differential Revision: https://phabricator.services.mozilla.com/D58200
--HG--
extra : moz-landing-system : lando
Changes:
Because part of the setup for `test-linux` jobs are done in `taskcluster/taskgraph/transforms/tests.py`, I suspect there isn't an easy way like in `test-macosx1014` to migrate a green suite one at a time, in piecemeal fashion.
This is the alternative proof of concept:
- rename the linux jobs with treeherder/job labels that include the version number like every other platform on our CI
- like `test-macosx1014`, create two test sets in `test-sets.yml` and stop running tests that are green on the older platform. If test has issues running on the new platform, keep it on the older, green platform at the moment while issues are worked out.
As proof of concept, apply this to `linux32/opt web-platform-tests` tasks
Differential Revision: https://phabricator.services.mozilla.com/D58025
--HG--
extra : moz-landing-system : lando
When I was working on release-promotion for Thunderbird, I needed a way to
control the scriptworker worker-types used on try vs. on release branches.
At the time, there did not exist a way to vary worker types so I introduced
a scriptworker-specific way to vary the worker type.
Since then, we add support for worker aliases, which can currently vary by
level. This reuses that machinery for selecting signing workers.
Differential Revision: https://phabricator.services.mozilla.com/D58018
--HG--
extra : moz-landing-system : lando
I noticed the version of `hg` used by mozharness tests is rather
old. This commit upgrades to version 5.2.1 (the latest).
Differential Revision: https://phabricator.services.mozilla.com/D58055
--HG--
extra : moz-landing-system : lando
Stop running raptor tests on Android P2 devices against 32-bit (armv7, or "api-16") builds. This will reduce our android-hw P2 load without losing meaningful test coverage (armv7 on G5 and aarch64 on P2 are more relevant).
Tests running on Android G5 are unchanged. Tests running against 64 bit builds (aarch64) are unchanged. Non-raptor tests are unchanged.
Differential Revision: https://phabricator.services.mozilla.com/D57717
--HG--
extra : moz-landing-system : lando
aarch64 mochitest-media, when scheduled as 2 chunks, has only one manifest in
one chunk -- and that manifest is skipped on aarch64! The other chunk runs
fine, so we may as well run the suite as a single chunk.
Differential Revision: https://phabricator.services.mozilla.com/D57804
--HG--
extra : moz-landing-system : lando
Enable using the 'settled' conditioned profile for geckoview and fenix apps.
Differential Revision: https://phabricator.services.mozilla.com/D55408
--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
The ppa we were using to get a python newer than 3.5 is no longer public.
Switch to a newer base image, that is on a distribution that provides python3.7
natively.
Differential Revision: https://phabricator.services.mozilla.com/D57659
--HG--
extra : moz-landing-system : lando
This is needed to support min() / max() / clamp(), as LengthPercentage will have
a potential heap allocation and the current copy-assignment operators just do
bitwise copies.
Differential Revision: https://phabricator.services.mozilla.com/D57300
--HG--
extra : moz-landing-system : lando
Make sure mozharness does not attempt to download the condprof source
in win-aarch64 (not supported yet)
Differential Revision: https://phabricator.services.mozilla.com/D57082
--HG--
extra : moz-landing-system : lando
Stop running aarch64 cppunit and mochitest-a11y on autoland and start running aarch64 web-platform tests on mozilla-central.
Keeps try access behind --full -- that seems like a good idea regardless.
Differential Revision: https://phabricator.services.mozilla.com/D57051
--HG--
extra : moz-landing-system : lando
This defines a new `dump_syms` toolchain that uses the rust implementation of `dump_syms`.
Differential Revision: https://phabricator.services.mozilla.com/D53318
--HG--
extra : moz-landing-system : lando
We can remove our backported objcopy patches, we'll need to update
llvm-mingw for toolchain fixes, and we need to add binutils to compile
this newer version of clang because the system binutils is too old.
Differential Revision: https://phabricator.services.mozilla.com/D50152
--HG--
rename : build/build-clang/clang-8-mingw.json => build/build-clang/clang-9-mingw.json
rename : taskcluster/scripts/misc/build-clang-8-mingw.sh => taskcluster/scripts/misc/build-clang-mingw.sh
extra : moz-landing-system : lando
We can remove our backported objcopy patches, we'll need to update
llvm-mingw for toolchain fixes, and we need to add binutils to compile
this newer version of clang because the system binutils is too old.
Differential Revision: https://phabricator.services.mozilla.com/D50152
--HG--
rename : build/build-clang/clang-8-mingw.json => build/build-clang/clang-9-mingw.json
rename : taskcluster/scripts/misc/build-clang-8-mingw.sh => taskcluster/scripts/misc/build-clang-mingw.sh
extra : moz-landing-system : lando
Changes:
Use ubuntu1804-test image instead of desktop1604-test for webrender(wrench) tasks.
Differential Revision: https://phabricator.services.mozilla.com/D56675
--HG--
extra : moz-landing-system : lando
Changes:
Migrate the harness test jobs to use ubuntu1804 test image instead of desktop1604-test.
Differential Revision: https://phabricator.services.mozilla.com/D56578
--HG--
extra : moz-landing-system : lando
This also reduces the configuration to just the -qr subset of the
configuration that runs for mochitest -fis.
Differential Revision: https://phabricator.services.mozilla.com/D56197
--HG--
extra : moz-landing-system : lando
Adjust ActiveData queries so that no query matches more than the ActiveData maximum
of 10000 records (crashtest excepted, until bug 1596567 is fixed). This provides a
dramatic improvement in the quality of run counts and run times reported for wpt and
reftests. Also adjusts some of the update mechanisms to handle duplicate paths better.
Also adds more (verbose) logging of match counts, report run times, etc in anticipation
of further refinements.
Differential Revision: https://phabricator.services.mozilla.com/D56616
--HG--
extra : moz-landing-system : lando
Changes:
Use ubuntu1804 test image as a direct drop-in replacement for linux profile generation tasks.
Differential Revision: https://phabricator.services.mozilla.com/D56605
--HG--
extra : moz-landing-system : lando
This is the final patch for perfdocs. It adds a taskcluster task called perfdocs-verify into mozlint that will run the performance documentation verification.
Depends on D53648
Differential Revision: https://phabricator.services.mozilla.com/D53649
--HG--
extra : moz-landing-system : lando
This is the final patch for perfdocs. It adds a taskcluster task called perfdocs-verify into mozlint that will run the performance documentation verification.
Depends on D53648
Differential Revision: https://phabricator.services.mozilla.com/D53649
--HG--
extra : moz-landing-system : lando
This defines a new `dump_syms` toolchain that uses the rust implementation of `dump_syms`.
Differential Revision: https://phabricator.services.mozilla.com/D53318
--HG--
rename : taskcluster/ci/toolchain/rust-size.yml => taskcluster/ci/toolchain/dump-syms.yml
rename : taskcluster/scripts/misc/build-rust-size.sh => taskcluster/scripts/misc/build-dump-syms.sh
extra : moz-landing-system : lando
xvfb was used to create a virtual framebuffer for running Firefox during
build jobs to support PGO profile generation. That now runs in a
separate task, so we don't need this flag for builds anymore.
Note that other Linux builds still need xvfb in order to run xpcshell in
'make check'.
Differential Revision: https://phabricator.services.mozilla.com/D56111
--HG--
extra : moz-landing-system : lando
llvm-mingw has found a way to build libssp indepdendent of gcc which
is great. We set up some stuff to support that and then use that method.
Differential Revision: https://phabricator.services.mozilla.com/D56248
--HG--
extra : moz-landing-system : lando
This includes more bitflag operators, which means we can remove some slightly
ugly code.
Differential Revision: https://phabricator.services.mozilla.com/D56308
--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
GCC8 happens not to generate the code that causes the crash, so do that for now
to unblock fuzzers from hitting this.
We still need to figure out what to do about the more general issue of course...
Differential Revision: https://phabricator.services.mozilla.com/D55985
--HG--
extra : moz-landing-system : lando
This adds test run time and test run/skipped/failed counts for most test types.
There are numerous shortcomings (sometimes exceeding the ActiveData 10K record limit,
test path/name mismatches, no totals for manifest/component/all, etc) but I would
like to see this running asap as I think it provides a good foundation for further
work and discussion.
Differential Revision: https://phabricator.services.mozilla.com/D55576
--HG--
extra : moz-landing-system : lando
Increase max-run-times to avoid intermittent task timeouts. Increasing chunks for
these tasks is not effective: chunks are very unbalanced due to a group of
long-running tests.
Differential Revision: https://phabricator.services.mozilla.com/D55182
--HG--
extra : moz-landing-system : lando
Instead of using a json file that contains URLs to task cluster artifacts, let's use a single zip file that contains all video files to analyze. This will reduce the number of artifacts we generate per raptor run and the number of network downloads.
The run-visual-metrics gets the tarball directly when it's used as a sub-task and produces its own result tarball
notice that at this point I don't see any reason to copy in the vismet results tarball all the files.
Maybe we should simply generate a *single* json file that contains a merge of all visualmetrics results?
But that could be done later. lmk
Differential Revision: https://phabricator.services.mozilla.com/D52907
--HG--
extra : moz-landing-system : lando
Fixes up ESR bouncer aliases now that ESR60 is EOL.
Adds check for latest products used by www.mozilla.org.
Enables the cron checks.
Fixes up a script error which meant we weren't checking all partial platforms in release automation.
Depends on D54656
Differential Revision: https://phabricator.services.mozilla.com/D54657
--HG--
extra : moz-landing-system : lando
Build a full sysroot by downloading the `wasi-sdk` repo, which has `llvm-project` and `wasi-libc` as submodules. `wasi-sdk` builds a `clang` in a unique configuration (with `wasm32-wasi` as a default target) and uses that `clang` to build the rest of the pieces for the wasm sysroot.
In principle it should be possible to build the sysroot using our in-house automation-built `clang`, but I kept running into strange, hard-to-diagnose issues when I attempted that. If someone else is able to straighten out all the compilation issues, we could replace this script and stop pulling in `wasi-sdk` entirely, which would result in a build that takes much less time overall. Until then, this will have to do to unblock the rest of the wasm sandboxing work.
Differential Revision: https://phabricator.services.mozilla.com/D54560
--HG--
extra : moz-landing-system : lando
