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
The documentation tasks do not include .taskcluster.yml, so fail when trying to
load the tests to generate documentation automatically.
Differential Revision: https://phabricator.services.mozilla.com/D57054
--HG--
extra : moz-landing-system : lando
Rerunning via action (i.e. from treeherder) currently fails for partials, as the
task isn't in the full task graph (since the parameters for the push-task don't
have the partials). Since (at least currently) all tasks not in the full graph
are release tasks, assume that they require reruns, not retriggers, to allow easier
handling of tasks via treeherder.
Differential Revision: https://phabricator.services.mozilla.com/D56516
--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
We've long handled chunks by defining the total number of chunks in our CI
configuration, and then passing that value down into the test harnesses at task
runtime (via the '--this-chunk' and '--total-chunks' parameters). The test
harness then runs an algorithm to determine which tests should be run in "this"
chunk.
There are several problems with this approach, but by far the biggest is that
we can't use test information in our scheduling algorithms. The information
simply isn't available yet. This patch switches things around such that we
determine which tests go in which tasks during the taskgraph generation. This
means we have perfect information around which tasks are running which tests,
and if e.g a ccov or machine learning algorithm deems a particular test
important, we can make sure to *only* schedule the tasks that contain that
test.
I'm planning to enable this a couple suites at a time so we don't accidentally
stop running tests. This specifically only enables this mode for
'mochitest-media', 'mochitest-browser-chrome' and 'mochitest-devtools-chrome'.
I chose these suites because they are the ones that are already using the
'chunk_by_runtime' algorithm.
Differential Revision: https://phabricator.services.mozilla.com/D52729
--HG--
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
MOZ_PGO_PROFILE_USE is used to enable certain features in the automation
mozconfigs for profile-use builds, including the MOZ_PROFILE_USE
configure option. They aren't easily combined into one flag due to the
extra settings that are enabled only in automation mozconfigs.
Renaming the former variable to TASKCLUSTER_PGO_PROFILE_USE makes it
slightly more obvious where it comes from and avoids confusion.
Differential Revision: https://phabricator.services.mozilla.com/D56117
--HG--
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
