By separating the "use this compiler" configuration from other items,
we avoid redundancies, and at the same time simplify how the aarch64
variants are configured by having the $os_variant.json files only
contain the `target`.
Overall, each build now only uses at most 4 configs:
- one for the compiler it uses
- one for the target (optional when the host is the same as the target)
- one for the patches applied to the clang/llvm source
- one for the build type (stage-1, profile or stage-4-pgo)
And a similar pattern for clang-tidy.
Also remove the setting for ld, which hasn't been used since bug
1799423, and ranlib and ar for builds using clang-cl, as it's not used
either.
Differential Revision: https://phabricator.services.mozilla.com/D220652
This splits the clang build in the necessary steps to get native
profiles for Intel and Arm64 mac, similarly to Linux.
Stage 1s are cross-compiled, and the profile step runs natively.
Differential Revision: https://phabricator.services.mozilla.com/D220530
We expose the /builds/worker/artifacts dir as artifacts, but the
buildconfig source-test task was writing elsewhere; this was missed in
the firefox-android migration from github.
Differential Revision: https://phabricator.services.mozilla.com/D220656
For now this uses Linux x64 profile for PGO as the macosx64-aarch64 task does, because we don't have aarch64 Windows worker now.
Differential Revision: https://phabricator.services.mozilla.com/D219012
This patch switches the builder from the intel osx 10.15 builders to the
Apple Silicon builders. 10.15 Is no longer a supported build target for
CaR (Chromium-as-Release) so let's use this opportunity to just go to the latest version
builders we have.
Additionally, this patch removes the custom CaR osx 10.15 tasks as that
is no longer a supported platform for the application.
Differential Revision: https://phabricator.services.mozilla.com/D218368
Clang trunk recently enabled reference types by default on wasm targets,
which for some reason breaks linking wasm. While the core problem is being
investigated, disable reference types.
Differential Revision: https://phabricator.services.mozilla.com/D215177
The robustcheckout.py that is in-tree ends up in docker images, used by
tasks running on docker-worker, but for tasks running on generic-worker,
we currently rely on whatever version of robustcheckout.py is there.
It currently seems out of date, but whenever we make changes to the
in-tree version, we don't end up with the fix on these jobs without some
additional manual work.
With this change, we do the same as with run-task and fetch-content: we
pull the in-tree version that we store as an artifact of the decision
task.
Differential Revision: https://phabricator.services.mozilla.com/D214234
The robustcheckout.py that is in-tree ends up in docker images, used by
tasks running on docker-worker, but for tasks running on generic-worker,
we currently rely on whatever version of robustcheckout.py is there.
It currently seems out of date, but whenever we make changes to the
in-tree version, we don't end up with the fix on these jobs without some
additional manual work.
With this change, we do the same as with run-task and fetch-content: we
pull the in-tree version that we store as an artifact of the decision
task.
Differential Revision: https://phabricator.services.mozilla.com/D214234
Upstream changes have changed the config path of depot_tools to default
to `$HOME/.config`. Instead we also have the option to set
`$XDG_CONFIG_HOME`. At the moment this only affects linux, with
windows/macos slated to have a similar change soon with possibly
different setup.
Differential Revision: https://phabricator.services.mozilla.com/D213438
Until recently, beta-YYYY-MM-DD dated channels was the only way to get
specific betas, but now it's possible to use x.y.z-beta.n, but
repack_rust.py doesn't handle that string as a version.
By considering only channels starting with beta- or nightly to be dated,
we allow x.y.z-beta.n to be considered as a version.
Differential Revision: https://phabricator.services.mozilla.com/D213367
This patch replaces the chromedrivers retrieved from the chromium
snapshots with the Chrome for Testing (CfT) chromedrivers (through the
"Canary" channel) for our Chromium-as-Release tests.
There is an occasional intermittent issue that occurs where the
chromedriver from the snapshots don't always work. Instead we can use
the `last-known-good-versions-with-downloads.json` provided by CfT to
get guaranteed stable chromedrivers.
Differential Revision: https://phabricator.services.mozilla.com/D212707
Building rustfmt would fail regularly, so the option was added to ignore
the problem, but that presumably hasn't been the case in a while.
The option was removed in rustc 1.80.
Differential Revision: https://phabricator.services.mozilla.com/D212491
Move the contents of the gradle-python-envs artifact into gradle-android-dependencies, stop referencing gradle-python-envs, and remove the android-gradle-python-envs toolchain task.
Differential Revision: https://phabricator.services.mozilla.com/D209149
This patch reworks the `fetch-chromium.py` script to only fetch the
chromedriver binary.
Previously because of Bug 1867068 it looks like the chromium fetch tasks
were not run since then and there is a mismatch between the CaR versions
and chromedriver version was causing some failures.
Differential Revision: https://phabricator.services.mozilla.com/D207090
For "robo"-type ui-tests, when crash logs are found and copied to the task artifacts, parse the crash log to report a treeherder-friendly crash message.
Differential Revision: https://phabricator.services.mozilla.com/D206565
This patch adds a toolchain task for pdfs to be used in the talos pdfpaint test. This is done with a fetch task for the Mozilla pdf.js repository, and a toolchain task that gathers the pdfs from that repository. The toolchain task also handles downloading additional PDFs from files that contain links to them. The additional shell script is used to run the script that gathers the PDFs and allow us to use the in-tree redo python package.
Differential Revision: https://phabricator.services.mozilla.com/D204903
The android-gradle-dependencies toolchain task already downloads gradle,
so we can reuse it instead of going through the wrapper.
Differential Revision: https://phabricator.services.mozilla.com/D205333
This introduces a toolchain task that just re-exposes the hostutils from
tooltool, which means adding that task as dependency of the relevant
tests gets it automatically. We can then get the hostutils from
MOZ_FETCHES_DIR directly.
Differential Revision: https://phabricator.services.mozilla.com/D205424
Mike Hommey