Rather than defining a distinct `Parameter` class for Gecko, this now uses the
`extend_parameters_schema` utility function (which mobile repos are already
using).
As a consequence, shared parameters are now defined in standalone taskgraph.
And only Gecko-specific parameters are listed in
`gecko_taskgraph/parameters.py`
The only exception is `project` which gets redefined so we can override the
standalone taskgraph default (since it derives `project` from the repo name,
which doesn't work for Gecko).
Differential Revision: https://phabricator.services.mozilla.com/D134515
This patch adds the matrix-react-bench to raptor-browsertime. It will run alongside the other benchmarks on trunk and mozilla-beta. It will also be possible to run these on chrome and chromium.
Differential Revision: https://phabricator.services.mozilla.com/D137344
The platform(s) were not specified, and it seems when that is the case that
it will only run on linux by default. The platforms are now explicitly
set to include Windows, Linux, and Mac.
Differential Revision: https://phabricator.services.mozilla.com/D136214
It turns out not only can we successfully build the Windows compiler
runtimes separately like on other platforms, but we can also
cross-compile them (like for other platforms)! Which saves a tremendous
amount of time when rebuilding the toolchains, since we can now produce
the clang-win-cross toolchain much earlier than waiting for a native
build of a windows clang compiler first.
While the script supports building an aarch64 compiler-rt, the llvm code
actually doesn't support it, so we don't create a task for it.
Differential Revision: https://phabricator.services.mozilla.com/D136837
And use the clang-13 json for all clang-13-based compiler-rt tasks.
This will ensure we apply all the patches that are intended to be
applied (we may want to split out the compiler-rt patches in the future,
though).
Differential Revision: https://phabricator.services.mozilla.com/D137119
Rather than defining a distinct `Parameter` class for Gecko, this now uses the
`extend_parameters_schema` utility function (which mobile repos are already
using).
As a consequence, shared parameters are now defined in standalone taskgraph.
And only Gecko-specific parameters are listed in
`gecko_taskgraph/parameters.py`
The only exception is `project` which gets redefined so we can override the
standalone taskgraph default (since it derives `project` from the repo name,
which doesn't work for Gecko).
Differential Revision: https://phabricator.services.mozilla.com/D134515
CLOSED TREE
We do want to use the llvm-symbolizer from the full clang build, which
has broader binary compatibility and is better guaranteed to match the
compiler used for builds that require llvm-symbolizer.
Differential Revision: https://phabricator.services.mozilla.com/D136971
It turns out not only can we successfully build the Windows compiler
runtimes separately like on other platforms, but we can also
cross-compile them (like for other platforms)! Which saves a tremendous
amount of time when rebuilding the toolchains, since we can now produce
the clang-win-cross toolchain much earlier than waiting for a native
build of a windows clang compiler first.
Differential Revision: https://phabricator.services.mozilla.com/D136837
We don't need clang-cl.exe from the win-cross toolchain anymore, which
makes the remaining usecase for that toolchain to provide compiler
runtimes for e.g. asan or profiling. For any build that doesn't involve
those, we can use the plain clang toolchain.
Differential Revision: https://phabricator.services.mozilla.com/D136834
This allows to start building other toolchains, compiler runtimes, much
earlier, since we don't have to wait for a complete 4-stage-optimized
compiler to start these, while the output produced by clang is
presumably the same whether it's a stage 1 or a stage 4 clang.
Differential Revision: https://phabricator.services.mozilla.com/D136844
This will ensure we don't accidentally cause bustage to graph generation with
any of the parameters checked into `taskcluster/test/params`.
This was previously being (sort of) tested by the `tgdiff` task. Now that this
test exists, we no longer need to rely on it.
I removed 'always-target' from the task since this now takes ~25 min to run and
which is the new bottleneck for reviewbot turn around times.
Differential Revision: https://phabricator.services.mozilla.com/D136514
In order to green up tests with dFPI enabled, this patch adds a dFPI
variant for mochitests and Web Platform Tests. Currently, dFPI has been
disabled for mochitests and Web Platform Tests. So, we need a tier 3
variant for us to verify if the tests were fixed with dFPI enabled. We
will add this variant to all possible mochitests and WPTs.
Note that we will remove this variant after we fix all tests.
Differential Revision: https://phabricator.services.mozilla.com/D136111
