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