For mozilla-central, all the code related to taskgraph lives in
taskcluster/taskgraph. Thunderbird's build requirements are evolving, and
we want to be able to have repository-specific code. The natural place for it
to live is an a package beside taskcluster/ci. Add that to python path,
and provide some hooks for adding to the various registries in taskgraph.
Differential Revision: https://phabricator.services.mozilla.com/D60540
--HG--
extra : moz-landing-system : lando
A few android-hw/bitbar jobs aren't getting exit code 4 set as a retry. Fix that.
Differential Revision: https://phabricator.services.mozilla.com/D59816
--HG--
extra : moz-landing-system : lando
This can sometimes reduce ESLint's runtime by 10 minutes!
Depends on D60686
Differential Revision: https://phabricator.services.mozilla.com/D60688
--HG--
extra : moz-landing-system : lando
This fixes an issue when running "mach taskgraph" with the --root parameter
from the commandline. We use this regularly when working on Thunderbird task
configuration.
The initial list of kind names is read with os.listdir(), which returns
non-unicode strings when given a non-unicode string. As a result, some tasks
fail to validate because there's a non-unicode string where a unicode string
is expected.
Differential Revision: https://phabricator.services.mozilla.com/D60775
--HG--
extra : moz-landing-system : lando
Since test-verify and coverage tasks sometimes run xpcshell, they require node fetches just
like xpcshell tasks: add the missing config for Android.
Differential Revision: https://phabricator.services.mozilla.com/D60716
--HG--
extra : moz-landing-system : lando
The scopes that are used are managed by the
`project:taskcluster:{trust_domain}:level-{level}-sccache-buckets`
role that is added a few lines above.
Differential Revision: https://phabricator.services.mozilla.com/D60710
--HG--
extra : moz-landing-system : lando
Avoid intermittent test failures for exceeding max-run-time by increasing
mochitest-webgl2-ext max-run-time from 30 minutes to 45 minutes. This is immediately
an issue on Windows 7 (MinGW) debug, but other platforms are close to the 30 minute
limit, so we may as well increase it across the board.
Differential Revision: https://phabricator.services.mozilla.com/D60560
--HG--
extra : moz-landing-system : lando
An experimental optimizer that schedules all test tasks that run tests that
are in the same directory (or subdir) of a modified file.
Differential Revision: https://phabricator.services.mozilla.com/D60527
--HG--
extra : moz-landing-system : lando
Changes:
Bug 1552563 introduced the notion that `compiz` should only be run where it was required. This was an attempt to save some seconds through the CI system as `compiz` takes 15 seconds to return an exit code.
Now that majority of tests are running under ubuntu1804, which runs the GNOME desktop environment, the flag `NEED_COMPIZ` is no longer necessary.
Differential Revision: https://phabricator.services.mozilla.com/D60342
--HG--
extra : moz-landing-system : lando
Avoid frequent intermittent test failures for exceeding max-run-time by increasing
mochitest-webgl1-ext max-run-time from 30 minutes to 45 minutes. This is immediately
an issue on Windows 7 MinGW debug, but other platforms are close to the 30 minute
limit, so we may as well increase it across the board.
Differential Revision: https://phabricator.services.mozilla.com/D60420
--HG--
extra : moz-landing-system : lando
Fetch, configure, and run node for Android on the test host, just like Linux tests do.
Make the node/HTTP/2 environment variables available to the tests on the device, and
use adb port forwarding to connect sockets. Finally, enable tests skipped for node.
Differential Revision: https://phabricator.services.mozilla.com/D60204
--HG--
extra : moz-landing-system : lando
In the past we had to stick to `clang-7` for `Coverity Static Analysis` but upgrading
to the latest version of `Coverity`, 2019.12, added support for the latest version
of `clang` from the artifacts system, `9.0.1`.
Differential Revision: https://phabricator.services.mozilla.com/D59994
--HG--
extra : moz-landing-system : lando
Fetch, configure, and run node for Android on the test host, just like Linux tests do.
Make the node/HTTP/2 environment variables available to the tests on the device, and
use adb port forwarding to connect sockets. Finally, enable tests skipped for node.
Differential Revision: https://phabricator.services.mozilla.com/D60204
--HG--
extra : moz-landing-system : lando
Changes:
Reorganize, reorder and review the sets defined in test-sets.yml to be more conducive to future changes.
Also, migrate `mochitest-valgrind` to run with linux1804.
Reorganize:
Group similar sets together, separated by whether it is a feature test set or operating system test set.
Review:
Remove test sets that are no longer used.
Rename test sets to be more descriptive of what it contains.
Differential Revision: https://phabricator.services.mozilla.com/D60198
--HG--
extra : moz-landing-system : lando
Changes:
`mochitest-e10s` is ready to migrate to ubuntu1804 for all platform variants.
Failures are intermittent on non-fission runs.
Note that on `mozilla-central`, `linux64-ccov/opt` does not run `mochitest-e10s` and this behavior is carried over. Fission variant is also not run on `mozilla-central`.
Try push with fission and ccov is included for sake of completeness.
Differential Revision: https://phabricator.services.mozilla.com/D59970
--HG--
extra : moz-landing-system : lando
Changes:
Migrate more tests to run under linux1804-64-ccov and disable them from linux64-ccov.
- code-coverage
- web-platform-tests (reftests, vanilla, crashtests)
- gtest (not run on mozilla-central or autoland)
- test-verify
- xpcshell
Differential Revision: https://phabricator.services.mozilla.com/D60192
--HG--
extra : moz-landing-system : lando
Attempt to stop running remaining raptor tests on android-hw-p2 against armv7 pgo builds
by removing the test sets from the platform definition. These had been left in place
so that they could continue to run on try, but I think that loss is quite small: tests
can still be run on android-hw-p2 against armv7 opt builds, all builds on G5, and all
aarch64 builds on P2.
Differential Revision: https://phabricator.services.mozilla.com/D60090
--HG--
extra : moz-landing-system : lando
This was regressed by the change from arm7 to aarch64 builds; easily corrected.
Differential Revision: https://phabricator.services.mozilla.com/D59968
--HG--
extra : moz-landing-system : lando
Changes:
Run the `mochitest-devtools-chrome` suite with ubuntu1804 for all platform variants, including `ccov`.
Differential Revision: https://phabricator.services.mozilla.com/D59571
--HG--
extra : moz-landing-system : lando
We are migrating the worker used by builds from AWS to GCP. We have had tier- 3 GCP builds for initial testing. We are replacing those with tier-3 AWS builds to ensure they keep working so we are able to switch back.
Differential Revision: https://phabricator.services.mozilla.com/D60042
--HG--
extra : moz-landing-system : lando
Changes:
Migrate over tests that are either green, or do not run by default on mozilla-central, to run under the linux1804-64-ccov/opt label.
Differential Revision: https://phabricator.services.mozilla.com/D59978
--HG--
extra : moz-landing-system : lando
Changes:
Enable reftest/reftest-no-accel on ubuntu1804/linux1018.
Remove reftest/reftest-no-accel from running on ubuntu1604/linux64.
Differential Revision: https://phabricator.services.mozilla.com/D59825
--HG--
extra : moz-landing-system : lando
Changes:
`mochitest-e10s` is ready to migrate to ubuntu1804 for all platform variants.
Failures are intermittent on non-fission runs.
Note that on `mozilla-central`, `linux64-ccov/opt` does not run `mochitest-e10s` and this behavior is carried over. Fission variant is also not run on `mozilla-central`.
Try push with fission and ccov is included for sake of completeness.
Differential Revision: https://phabricator.services.mozilla.com/D59970
--HG--
extra : moz-landing-system : lando
Changes:
`linux1804-64-asan-qr/opt` was originally disabled because reftest fuzzy values were incorrect.
This change will re-enable the platform combination on CI, and remove the corresponding linux64 variant since all tests that run on the `asan-qr` variant is now migrated.
Differential Revision: https://phabricator.services.mozilla.com/D59974
--HG--
extra : moz-landing-system : lando
Currently, when task system-symbols-mac doesn't produce artifacts because of no data, then the task system-symbols-mac-upload-symbols is failing too.
So this patch aims to not fail the task in such a case.
Differential Revision: https://phabricator.services.mozilla.com/D59848
--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
Move all mochitest, crashtests, and plain reftests currently running on android-hw-p2
against arm7 builds to aarch64 builds (the great majority of geckoview users on P2 are
now using aarch64 builds -- we want to stay relevant). jittest and jsreftest continue
to run on arm7, providing essential arm7 support; aarch64 coverage continues to be
provided by SM(p) on Windows/aarch64 laptops.
Differential Revision: https://phabricator.services.mozilla.com/D59804
--HG--
extra : moz-landing-system : lando
Changes:
Rename the `web-platform-tests-1804` set to `web-platform-tests`.
Create a new set with name `web-platform-tests-wdspec` which will hold only the `wdspec` test to be run on ubuntu1604.
Use the now-named `web-platform-tests` set to be used for ubuntu1804 platforms.
Differential Revision: https://phabricator.services.mozilla.com/D59449
--HG--
extra : moz-landing-system : lando
Changes:
Run `mochitest-remote` with ubuntu1804, including the `ccov` platform variant.
Disable the test suite from running on ubuntu1604 under `linux64` label, including the `ccov` variant.
Differential Revision: https://phabricator.services.mozilla.com/D59585
--HG--
extra : moz-landing-system : lando
Changes:
Diffoscope linux32 (diff-reproducible-linux32) was triggering linux-shippable jobs on autoland.
For good measure, specify for `geckodriver-repack` that it should not run on autoland.
Also restrict `linux-shippable` build on gcp from taking place on autoland. It is a tier 3 job so not visible normally.
Differential Revision: https://phabricator.services.mozilla.com/D59444
--HG--
extra : moz-landing-system : lando
Changes:
Restore the original state of `web-platform-tests` test set in `test-sets.yml`.
Changes in D59403 had the unintended side effect of removing `web-platform-tests-reftests` and `web-platform-tests-crashtests` from the main test set, which was used for both `linux64` and `windows` platforms.
`position-sticky-scroll-with-clip-and-abspos-ref.html` was failing because the test no longer needed a `fuzzy` annotation for `webrender` variant.
Differential Revision: https://phabricator.services.mozilla.com/D59752
--HG--
extra : moz-landing-system : lando
Changes:
Re-enable the `test-linux1804-ccov/opt` variant.
Create a new `linux1804-ccov-tests` test set.
Add `awsy` to ubuntu1804 and remove it correspondingly from ubuntu1604.
Add `mochitest-webgl` tests to ubuntu1804 an remove it from ubunt1604.
Differential Revision: https://phabricator.services.mozilla.com/D59593
--HG--
extra : moz-landing-system : lando
Changes:
Rename the `web-platform-tests-1804` set to `web-platform-tests`.
Create a new set with name `web-platform-tests-wdspec` which will hold only the `wdspec` test to be run on ubuntu1604.
Use the now-named `web-platform-tests` set to be used for ubuntu1804 platforms.
Differential Revision: https://phabricator.services.mozilla.com/D59449
--HG--
extra : moz-landing-system : lando
CLOSED TREE
Backed out changeset bf9cd5aea492 (bug 1602863)
Backed out changeset c656cb682586 (bug 1602108)
--HG--
extra : rebase_source : 16b901e23b6c0cadaea5ef159901f0a1dea3aa50
Changes:
Run the `mochitest-devtools-chrome` suite with ubuntu1804 docker image.
Update references to linux64 in `mochitest.yml` for mochitest-devtools-chrome to refer to `linux1804-64`.
Depends on D59570
Differential Revision: https://phabricator.services.mozilla.com/D59571
--HG--
extra : moz-landing-system : lando
We don't need to package tests for builds that we don't actually run
tests from, but it is tricky to align this correctly by setting
MOZ_AUTOMATION_PACKAGE_TESTS=0 in relevant mozconfigs. Instead we can
set the environment variable in the task definition, and use a full
taskgraph verification check to ensure that the flag is only set on
builds that have tests.
The one tricky task is win64-aarch64-shippable/opt, which copies tests
from another build rather than building them itself. For this reason, it
explicitly sets MOZ_AUTOMATION_PACKAGE_TESTS: '0' in the environment
even though that is now the default. This is why the exception is only
raised if MOZ_AUTOMATION_PACKAGE_TESTS is not set at all, rather than
checking that it is set to 1.
Differential Revision: https://phabricator.services.mozilla.com/D59426
--HG--
extra : moz-landing-system : lando
Changes:
Rename the `web-platform-tests-1804` set to `web-platform-tests`.
Create a new set with name `web-platform-tests-wdspec` which will hold only the `wdspec` test to be run on ubuntu1604.
Use the now-named `web-platform-tests` set to be used for ubuntu1804 platforms.
Differential Revision: https://phabricator.services.mozilla.com/D59449
--HG--
extra : moz-landing-system : lando
Changes:
Add webgl tests to the linux1804-tests set, not just the linux1804-qr-tests set.
Differential Revision: https://phabricator.services.mozilla.com/D59457
--HG--
extra : moz-landing-system : lando
Changes:
Add `jittest` to the linux1804-test set.
This will have no effect until `ccov` variant is enabled for ubuntu1804.
Differential Revision: https://phabricator.services.mozilla.com/D59456
--HG--
extra : moz-landing-system : lando
The only thing it used it for was for a default filename, but we
always pass an explicit name, so remove the platform option and the
default filename.
Differential Revision: https://phabricator.services.mozilla.com/D59399
--HG--
extra : moz-landing-system : lando
Changes:
Now that mfenced-12.html is disabled, run `reftest-no-accel` on ubuntu1804.
Differential Revision: https://phabricator.services.mozilla.com/D59448
--HG--
extra : moz-landing-system : lando
The only thing it used it for was for a default filename, but we
always pass an explicit name, so remove the platform option and the
default filename.
Differential Revision: https://phabricator.services.mozilla.com/D59399
--HG--
extra : moz-landing-system : lando
We're going to build `lucetc` for other platforms; let's prefix this
task with the platform name like we do for other toolchains.
Differential Revision: https://phabricator.services.mozilla.com/D59498
--HG--
extra : moz-landing-system : lando
If you pass in multiple paths to mozlint, it will attempt to parallelize them
across processes. With this change, we pass in all top-level files and
directories into mozlint rather than the topsrcdir itself. This triggers the
parallelization.
The 'yaml' and 'codespell' linters were excluded because they had issues.
Differential Revision: https://phabricator.services.mozilla.com/D59527
--HG--
extra : moz-landing-system : lando
Because the Puppeteer unit tests run as source tasks and not test
tasks, we can't rely on the generic technique for enabling Fission
available to other test tasks based on mozharness.
Since the puppeteer task is a simple, opt-in, non-scheduled job we
duplicate it as puppeteer-fis and pass --enable-fission to "./mach
puppeteer-test" instead. This achieves the same effect.
Differential Revision: https://phabricator.services.mozilla.com/D58598
--HG--
extra : moz-landing-system : lando
Changes:
Run `web-platform-tests-crashtests`, `web-platform-tests-reftests` with ubuntu1804 docker image.
This is a piecemeal migration, since the main `web-platform-tests` is not ready for ubuntu1804 yet due to several issues.
Depends on D59386.
Differential Revision: https://phabricator.services.mozilla.com/D59403
--HG--
extra : moz-landing-system : lando
Changes:
Run mochitest-webgl suites on ubuntu1804.
Update the expectation of a test to remove the `headless` specification.
Differential Revision: https://phabricator.services.mozilla.com/D59401
--HG--
extra : moz-landing-system : lando
Changes:
Run `mochitest-a11y` on ubuntu1804 image.
On the `ubuntu1804` image, bug 1429575 is a relatively frequent occurrence.
Differential Revision: https://phabricator.services.mozilla.com/D59220
--HG--
extra : moz-landing-system : lando
Previously we simply ignored skipped tests when performing test chunking in the
taskgraph. This could sometimes result in a task that runs a single manifest
that happens to be skipped on that task's configuration. This results in an error
that no tests were run from the harness.
This patch attempts to guess a mozinfo based on a task's definition. Then it
uses those values to take skipped tests into account when running the chunking
algorithm. That way the chances of scheduling a manifest that would be skipped
anyway are much lower.
Depends on D58987
Differential Revision: https://phabricator.services.mozilla.com/D58988
--HG--
extra : moz-landing-system : lando
The new code is a superset of the old, so I've left it much the same to avoid conflicts until we come up with a more long term solution.
Differential Revision: https://phabricator.services.mozilla.com/D59181
--HG--
extra : moz-landing-system : lando
Changes:
Do not run `linux32` builds on `try` or `autoland` by default, but ensure it is able to run on all other repos (eg. `mozilla-beta`).
Filter out all tasks with `linux-shippable` in the name, including builds, auxiliary tasks (balrog, etc).
Differential Revision: https://phabricator.services.mozilla.com/D58982
--HG--
extra : moz-landing-system : lando
Changes:
Run `web-platform-tests-wdspec-headless` and `mochitest-webgpu` with ubunt1804 image.
Changes to the `linux64` references in `web-platform.yml` and `mochitest.yml` are not necessary.
Differential Revision: https://phabricator.services.mozilla.com/D59209
--HG--
extra : moz-landing-system : lando
Changes:
**linux1804-64-asan-qr**, bug 1607620
This platform references the `linux-qr-smoketests` test set which is not one of the `linux1804` labeled test sets.
So the changes in D58964 meant that these tests were enabled for `linux1804-qr-asan/opt`, which is fine except the `reftest` suites has 1 failure.
Temporarily disable this platform for the time being while reftest failure is worked out. This does not mean we lose coverage, since the ubuntu1604 variant `linux64-asan-qr/opt` is still running on all repos.
**linux1804-64-ccov platforms**, bug 1607887
ccov on ubuntu1804 is not ready yet, as per :marco in D58739. Technically speaking the disabling should have taken place in that patch, but that escaped my mind then.
Differential Revision: https://phabricator.services.mozilla.com/D59214
--HG--
extra : moz-landing-system : lando
Changes:
Run the `mochitest-headless` suite with ubuntu1804 image
No updates to linux64 references in `mochitest.yml` is necessary.
Differential Revision: https://phabricator.services.mozilla.com/D59195
--HG--
extra : moz-landing-system : lando
Changes:
Run the reftest suite with ubuntu1804 test image.
Depends on D54851.
Differential Revision: https://phabricator.services.mozilla.com/D58816
--HG--
extra : moz-landing-system : lando
Changes:
Due to changes I made in D58204 and D58464, `awsy` was migrated to run under the `linux1804-64` label. This was fine except `awsy.yml` used `linux64` to set scheduling.
This patch will update the references to `linux1804-64` and restore proper scheduling of tasks.
Differential Revision: https://phabricator.services.mozilla.com/D59017
--HG--
extra : moz-landing-system : lando
Changes:
Update references to `linux64` in the YAML files to read `linux1804-64`.
Differential Revision: https://phabricator.services.mozilla.com/D59024
--HG--
extra : moz-landing-system : lando
Changes:
Run mochitest-screenshots with ubuntu1804, and remove from running under `linux64` label.
Also update the references in `mochitest.yml` for the `run-on-projects` scheduler.
Differential Revision: https://phabricator.services.mozilla.com/D58864
--HG--
extra : moz-landing-system : lando
Changes:
The `test-sets:` line was missing, which caused warnings.
Also correct the name of the test platform combination.
Differential Revision: https://phabricator.services.mozilla.com/D58964
--HG--
extra : moz-landing-system : lando
Changes:
Run `xpcshell` test suite on ubuntu1804 for all platforms except `linux64-ccov`.
Modify the test in `test_fuzzy.py` to refer to the new `test-linux1804` xpcshell task label.
Add a new test in `test_fuzzy.py` to test the `-q` functionality without a test path.
Differential Revision: https://phabricator.services.mozilla.com/D58740
--HG--
extra : moz-landing-system : lando
Changes:
Remove the linux64/opt stylo combination since the only test it ran was the `awsy-stylo-sequential` which is now duplicated by linux1804-64-stylo-sequential/opt.
Differential Revision: https://phabricator.services.mozilla.com/D58873
--HG--
extra : moz-landing-system : lando
Changes:
Run `marionette-headless` with ubuntu1804 instead of desktop1604.
`marionette-headless-fission` is ignored because it already fails with normal desktop1604-test image.
Differential Revision: https://phabricator.services.mozilla.com/D58868
--HG--
extra : moz-landing-system : lando
This allows easy testing against staging worker types, without needing to
change anything in-tree.
Differential Revision: https://phabricator.services.mozilla.com/D58017
--HG--
extra : moz-landing-system : lando
Changes:
Revert the changes to the treeherder name since the partials script does depend on the name as it appears in treeherder to the pre-D58406 state.
Differential Revision: https://phabricator.services.mozilla.com/D58897
--HG--
extra : moz-landing-system : lando
Changes:
Demote linux32-shippable/opt tasks to tier 2 on all repositories. Other linux32 jobs are defined but do not appear to run.
Limit the build of linux32-shippable/opt to `try`/`mozilla-central`.
Differential Revision: https://phabricator.services.mozilla.com/D58207
--HG--
extra : moz-landing-system : lando
Changes:
Demote linux32-shippable/opt tasks to tier 2 on all repositories. Other linux32 jobs are defined but do not appear to run.
Limit the build of linux32-shippable/opt to `try`/`mozilla-central`.
Differential Revision: https://phabricator.services.mozilla.com/D58207
--HG--
extra : moz-landing-system : lando
Changes:
Exclude the `linux-ccov` platform from ubuntu1804 migration plans for the time being.
The `linux64-ccov` test platform originally ran the `common-tests` test set so change the `linux-common-tests` to refer to `common-tests`. This should restore all sets of tests to the `linux64-ccov` label.
Differential Revision: https://phabricator.services.mozilla.com/D58739
--HG--
extra : moz-landing-system : lando
It will be relanded once these are complete. This prevents from those tasks
getting scheduled for every push until the initial ones have been completed.
Thunderbird plans to include libotr and its dependencies in official builds in
order to support Off-The-Record messaging.
When building these libraries for Windows, GCC/MinGW is currently needed.
This Docker image includes the Debian MinGW compiler and will only be used for
building libotr, libgcrypt, and libgpg-error, not Thunderbird itself.
See the docker-image kind in Thunderbird's repository for the associated
Taskcluster configuration.
Differential Revision: https://phabricator.services.mozilla.com/D57722
--HG--
extra : moz-landing-system : lando
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
Fix a test which calls the ip address
testing/mozbase/moznetwork/tests/test_moznetwork.py
Differential Revision: https://phabricator.services.mozilla.com/D58192
--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
`memoize` doesn't support keyword arguments currently, so only memoize the internal helper, and not
the public functions.
Differential Revision: https://phabricator.services.mozilla.com//D58167
--HG--
extra : histedit_source : 3b0d439449de7a2a0ceea719a002eb0856115aa1
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
requests-unixsocket has a default timeout that is too large to reliably
load the larger docker-images we have. Double the timeout to enable
images to build reliably.
Differential Revision: https://phabricator.services.mozilla.com/D58149
--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
This patch causes the newest version of NodeJS 8.17.0 to be used to build the mozilla toolchains installed on the CI machines as well as by `mach bootstrap`, which in turn gets an important security fix by updating to npm 6.13.4.
This patch also causes mach commands which call npm to abort if the version in use is older than 6.13.4 to avoid (especially) exploits on local developers that exfiltrate their data.
Differential Revision: https://phabricator.services.mozilla.com/D57674
--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
`copy_attributes_from_dependent_task` was originally used for tasks downstream
so required `build_type` and `build_platform`, but the function is useful
enough, that it should not require anything.
Differential Revision: https://phabricator.services.mozilla.com//D57155
--HG--
extra : histedit_source : 92f5169aab530426d31ab86327f7b618dfb778eb
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
The browser build generates this file during the packaging step, which does not exist for JS shell builds. I made a brief attempt to call informulate.py as it does, but that seemed to require some things that are not available during the shell build. So I went with the cheap and easy approach to provide just the fields :jkratzer uses.
Differential Revision: https://phabricator.services.mozilla.com/D57028
--HG--
extra : moz-landing-system : lando
We build bindgen without the `which` feeature, which means it won't try to
look for `rustfmt` in $PATH. So point at it explicitly so that the bindings are
properly formatted.
We do the same for regular Gecko builds in `build/mozconfig.rust`.
Differential Revision: https://phabricator.services.mozilla.com/D56957
--HG--
extra : moz-landing-system : lando
Nick Alexander
Rob Lemley
Andreea Pavel
Justin Wood
Dzmitry Malyshau
shindli
Chris Manchester
Andrew Erickson
Tom Prince
Andrew Halberstadt
Marian Raiciof
Bob Clary
Geoff Brown
Csoregi Natalia
Ricky Stewart
Edwin Takahashi
Andi-Bogdan Postelnicu
ffxbld
Sebastian Hengst
Narcis Beleuzu
Tyson Smith
Razvan Maries
Daniel Varga
Mike Hommey
Jeff Gilbert
Wander Lairson Costa
Bogdan Tara
Cosmin Sabou
Marco Castelluccio
Stephen Donner
Calixte Denizet
Rob Wood
Bastien Abadie
Ryan VanderMeulen
Mihai Alexandru Michis
Dorel Luca
Mike Shal
Adam Gashlin
Nathan Froyd
Andreas Tolfsen
Matt Brandt
Simon Fraser
alexandru.ionescu
Mihai Tabara
Henrik Skupin
Sylvestre Ledru
Ben Hearsum
Ciure Andrei
James Graham
Steve Fink
Geoff Lankow
Noemi Erli
Gurzau Raul
Connor Sheehan
Dan Mosedale
Tarek Ziadé
Anthony Hughes
Oana Pop Rus
Aki Sasaki
Emilio Cobos Álvarez
Gabriele Svelto