This key doesn't appear to be used by anything. Let's get rid of it to remove
some of the complexity around chunking.
Differential Revision: https://phabricator.services.mozilla.com/D48422
--HG--
extra : moz-landing-system : lando
Check the return code of write() to determine if the output line has actually been written completely; if not, write the remainder.
Tests suggest that incomplete writes are possible when the buffer exceeds a few thousand bytes. Very long log lines are unusual but this is important for cases like reftest failures where an encoded screenshot is dumped to the log.
Differential Revision: https://phabricator.services.mozilla.com/D48218
--HG--
extra : moz-landing-system : lando
This enables wpt-fis for the same configurations as mochitest-fis,
initially as T3 so that any stability issues can be worked out.
Differential Revision: https://phabricator.services.mozilla.com/D49241
--HG--
extra : moz-landing-system : lando
Most of these tests have been disabled for a long time; they run well
in the current test environment.
With the additional tests running, task times increase; I have added one
more test chunk for android mochitest-plain.
These tests were identified from a random sampling of mochitest manifests;
I intend to enable more mochitests in future patches.
Differential Revision: https://phabricator.services.mozilla.com/D48912
--HG--
extra : moz-landing-system : lando
The intention is to run `tp6m-1` and `tp6m-cold-1` using Browsertime
against the GVE vehicle on integration and try, so as to smoketest the
Browsertime harness as we stabilize it. At the same time, this also
allows try runs against the Fenix and refbrow vehicles.
Differential Revision: https://phabricator.services.mozilla.com/D48772
--HG--
rename : taskcluster/ci/test/raptor-fenix.yml => taskcluster/ci/test/browsertime-fenix.yml
rename : taskcluster/ci/test/raptor-gve.yml => taskcluster/ci/test/browsertime-gve.yml
rename : taskcluster/ci/test/raptor-refbrow.yml => taskcluster/ci/test/browsertime-refbrow.yml
extra : moz-landing-system : lando
This version includes a fix necessary to distributing builds to multiple
servers as well as several important fixes to the client that will help
people attempting to distribute compiles. Once a bit more testing has been
seen we will update the required version used locally to 0.2.12.
Differential Revision: https://phabricator.services.mozilla.com/D48441
--HG--
extra : moz-landing-system : lando
This patch enables the iris test suite to run in CI against Windows and Linux shippable builds on mozilla-central and try. The framework is in place for Iris to run against MacOS in CI, but it is currently disabled while bootstrapping issues are sorted out.
Linux uses a new docker image based on the debian10-test parent image that installs preinstalls most of Iris's dependencies. Windows installs a few dependencies using the scoop package manager. Both then install the rest of the python dependencies via pip.
This adds a new toolchain artifact to fetch the iris_firefox git repo without touching the outside network.
Differential Revision: https://phabricator.services.mozilla.com/D41638
--HG--
extra : moz-landing-system : lando
This does many things:
1) stops producing (and consuming) `FennecJNI*` JNI wrappers
2) removes the :app and :thirdparty Gradle projects
3) removes relevant pieces of the Gradle target configuration
4) updates lints
5) purges old configurations
After this commit, the `mobile/android` project/application builds
only GeckoView.
Differential Revision: https://phabricator.services.mozilla.com/D46536
--HG--
extra : moz-landing-system : lando
This changes certain fission tests to run tier 1 and start running on integration branches:
linux64-qr/debug mochitest-plain
linux64-qr/debug mochitest-media
linux64-qr/debug mochitest-webgl*
linux64/debug browser-chrome
All other fission tests continue to run as tier 2.
Differential Revision: https://phabricator.services.mozilla.com/D47295
--HG--
extra : moz-landing-system : lando
This patch prevents chrome and chromium raptor tests from running on all mozilla-central commits. They will be triggered on Mondays, Wednesdays, and Fridays by a cron task instead.
Differential Revision: https://phabricator.services.mozilla.com/D47773
--HG--
extra : moz-landing-system : lando
Bug 1571573 removed the manual download of node by mozharness. That made
the tasks use whatever comes from fetches, and for aarch64 tests, it
turned out to be a win64 node binary, which doesn't work on aarch64.
Differential Revision: https://phabricator.services.mozilla.com/D47707
--HG--
extra : moz-landing-system : lando
This patch modifies the existing android_power_testing cron task to make it a more general performance testing task that runs a set of tests 3 times a week. The tests that will be running in this task are all chrome, chromium, android CPU+memory, and android power tests.
Differential Revision: https://phabricator.services.mozilla.com/D47140
--HG--
extra : moz-landing-system : lando
To support NDK r20, wrench needs to be built with a more recent, upstream
(though still unpublished) version of cargo-apk. This has some consequences
which have been adjusted for:
* Gradle is no longer required to build wrench.
* The output apk file paths have changed.
* The apks are now signed automatically.
* The default activity name has changed.
* Android permissions must be explicitly requested.
* We must ensure winit is built with a matching version of android_glue.
Differential Revision: https://phabricator.services.mozilla.com/D47129
--HG--
extra : moz-landing-system : lando
With clang-8 sources, this task was already pretty close to the limit with typical times of 54-58 minutes.
In clang-9, enough new code was added that we're seeing frequent intermittent timeouts. Even the few successful builds come in just under the wire at 60 minutes.
Note for sheriffs, if the clang-9 update gets backed out, this patch can stay, we'll need it anyway.
Differential Revision: https://phabricator.services.mozilla.com/D47288
--HG--
extra : moz-landing-system : lando
This patch adds fullscreen and windowed youtube tests for the V9 and H264 encoding at 1080p30 and 1080p60. Each subtest runs for 20 page cycles which amounts to about 5 minutes each. It also begins adding these to power test tasks running on the macosx-1014 reference hardware.
Differential Revision: https://phabricator.services.mozilla.com/D45067
--HG--
extra : moz-landing-system : lando
This changes certain fission tests to run tier 1 and start running on integration branches:
linux64-qr/debug mochitest-plain
linux64-qr/debug mochitest-media
linux64-qr/debug mochitest-webgl*
linux64/debug browser-chrome
All other fission tests continue to run as tier 2.
Differential Revision: https://phabricator.services.mozilla.com/D47295
--HG--
extra : moz-landing-system : lando
Change the taskcluster max-run-time for mochitests and reftests to use the
defaults, now that android tests no longer run anywhere near 7200 seconds.
(Also noticed some unrelated tc configuration that is obsolete - tidied that.)
Also remove the special 600 second reftest timeout for android debug reftests.
Differential Revision: https://phabricator.services.mozilla.com/D47301
--HG--
extra : moz-landing-system : lando
Using git-archive for the fetch task means that we don't get the
submodules of a git repository included in the archive. There isn't a
straightforward way to get submodules from a bare repo included with
git-archive, so instead we can simply clone & checkout with
--recurse-submodules and then use a standard tar command to bundle up
the tree.
Adding --recurse-submodules to the commands has no effect on a repo
without submodules, so we can add it to all invocations for simplicity.
Differential Revision: https://phabricator.services.mozilla.com/D46827
--HG--
extra : moz-landing-system : lando
python's `urllib.request.urlopen(url)` can fail when a system doesn't know how to verify a ca certificate. this patch makes use of the cafile provided by the `certifi` module, if/when it is installed, to verify certificates.
Differential Revision: https://phabricator.services.mozilla.com/D47044
--HG--
extra : source : 92b9ffc8f37ddd16ca3f426d64df059eea38d5fa
python's `urllib.request.urlopen(url)` can fail when a system doesn't know how to verify a ca certificate. this patch makes use of the cafile provided by the `certifi` module, if/when it is installed, to verify certificates.
Differential Revision: https://phabricator.services.mozilla.com/D47044
--HG--
extra : moz-landing-system : lando
An error crept in, resulting in:
```
[task ...] InterpreterError: InterpreterError: infix: [..] expects integer [..] integer
```
At some point, `suite` became a string name and not an object with a
string `name` member. However, in the interim, the diversity of
`command` structures has made the template approach untenable.
Therefore, this commit converts `GeckoProfile` to a `TryConfig`. The
existing test clearly wasn't helpful, and it doesn't really map to a
`TryConfig` test, so it was removed.
Differential Revision: https://phabricator.services.mozilla.com/D41603
--HG--
extra : moz-landing-system : lando
Stop running all Raptor tests that run against Fennec. Raptor tests running
against geckoview and geckoview products continues.
Differential Revision: https://phabricator.services.mozilla.com/D44511
--HG--
extra : moz-landing-system : lando
The recent increase was not quite enough: Allow another 30 minutes for linux64
ccov browser-chrome.
Differential Revision: https://phabricator.services.mozilla.com/D46787
--HG--
extra : moz-landing-system : lando
Our build toolchains don't contain libstdc++ headers for aarch64, so our
aarch64 builds rely on whatever libstdc++ headers the system has
installed. To bring in newer headers on our aarch64 builds, then, we
need to update the system images for those builds, which this patch does.
Depends on D45861
Differential Revision: https://phabricator.services.mozilla.com/D45862
--HG--
extra : moz-landing-system : lando
On older Debian versions, `libstdc++-$VERSION-dev` is implicitly brought
in by other development packages. On newer versions, this dependency
has been removed. Let's go ahead and explicitly declare which version
we want to install for each Debian version.
Differential Revision: https://phabricator.services.mozilla.com/D45861
--HG--
extra : moz-landing-system : lando
It was added in bug 1575760 and turns out to be causing a lot more
problems than anticipated.
However, the previous status quo is also not ideal, so we do
auto-generate .cargo/config.in instead, with a little trick that allows
to just copy it to .cargo/config instead of how individual scripts would
previously manually preprocess it.
Differential Revision: https://phabricator.services.mozilla.com/D46138
--HG--
extra : moz-landing-system : lando
Increase max-run-time for linux and windows ccov browser-chrome tasks to avoid
frequent task timeouts. (linux platform name was incorrect in existing configuration).
I would prefer to see shorter max-run-time but there may be no alternative for
these tasks.
Differential Revision: https://phabricator.services.mozilla.com/D46486
--HG--
extra : moz-landing-system : lando
Mozharness no longer drives building with PGO; it is all handled in
Taskcluster and the build system.
Depends on D46070
Differential Revision: https://phabricator.services.mozilla.com/D46071
--HG--
extra : moz-landing-system : lando
This task has been added to create all the missing cold tests for mobile websites.
Differential Revision: https://phabricator.services.mozilla.com/D45634
--HG--
extra : moz-landing-system : lando
This patch adds google chrome release tests for windows10-64, windows7-32, linux64, and macosx. It will run anywhere chromium is currently running, and uses the same settings as chromium for tier, max-run-time, etc.. All chromium test tasks will remain as they are - they will be run in a cron task in the future.
Differential Revision: https://phabricator.services.mozilla.com/D45385
--HG--
extra : moz-landing-system : lando
ML now means Machine Learning for most people, we should be more explicit for new comers
Differential Revision: https://phabricator.services.mozilla.com/D45488
--HG--
extra : moz-landing-system : lando
If the run task generates bad profile data, the merge step in the
profile-use task will fail. However, retrying the profile-use task
doesn't fix the problem, and there isn't a straightforward way to retry
the run task in this situation. Instead we can add a clang toolchain to
all the run tasks, and perform the merge there.
This means the output from the run task will always be a successfully
merged file called 'merged.profdata', and we no longer need to perform
the merge as part of the profile-use build as a GENERATED_FILES step.
Depends on D45262
Differential Revision: https://phabricator.services.mozilla.com/D45263
--HG--
extra : moz-landing-system : lando
The aarch64 cross toolchain is unused otherwise. The aarch64-linux
builds also exist for the express purpose of eventually standing up some
kind of fuzzing/ccov build, so we might as well start using a toolchain
that supports those use cases.
Differential Revision: https://phabricator.services.mozilla.com/D45210
--HG--
extra : moz-landing-system : lando
This includes a fix for the dist server people will need to efficiently
distribute builds. The version required by configure is not bumped with this
change, as this difference is crucial to the server but not relevant to the
client.
Differential Revision: https://phabricator.services.mozilla.com/D45230
--HG--
extra : moz-landing-system : lando
With the migration from AWS to GCP, we also need to migrate sccache
buckets from S3 to Google Storage.
The problem is how we deal with regions, since there isn't an exact
correspondence on the region names between the two cloud providers.
To make the transition smoother, docker-worker (and soon generic-worker)
provides a new environment variable called TASKCLUSTER_WORKER_LOCATION,
with information about the cloud provider the task is running on. Using
this new variable, we configure sccache to use the corresponding storage
service of the cloud provider where the task runs.
The bucket names in Google Storage are shorter because GCS imposes a
limit of 30 characteres for the names.
Ref: https://github.com/taskcluster/taskcluster-rfcs/pull/148/files
Differential Revision: https://phabricator.services.mozilla.com/D44845
--HG--
extra : moz-landing-system : lando
I found that I did not restore the `set -e` flag after temporarily disabling it in the debian10-specific piece of experimental code in `test-linux.sh`, and this caused a bunch of my try pushes to register as successful despite having multiple unexpected failures.
Differential Revision: https://phabricator.services.mozilla.com/D44774
--HG--
extra : moz-landing-system : lando
Increase max-run-time to avoid intermittent failures due to variance in robustcheckout
performance.
Differential Revision: https://phabricator.services.mozilla.com/D45200
--HG--
extra : moz-landing-system : lando
Bogdan Tara
Rob Wood
Tom Prince
Andrew Halberstadt
Andrew Erickson
Matt Brandt
Nick Thomas
Wes Kocher
Geoff Brown
James Graham
Daisuke Akatsuka
Brian Grinstead
Dorel Luca
Sylvestre Ledru
Mihai Tabara
ffxbld
Johan Lorenzo
Nick Alexander
Coroiu Cristina
Marco Castelluccio
Marian Raiciof
Florin Strugariu
Chris Manchester
Chris AtLee
Gurzau Raul
Steve Fink
Stephen Donner
Gregory Mierzwinski
Mike Hommey
Ciure Andrei
Ryan VanderMeulen
David Major
Ricky Stewart
Jamie Nicol
Brindusan Cristian
Kris Maglione
Mike Shal
Rob Thijssen
Noemi Erli
Andreea Pavel
Oana Pop Rus
Henrik Skupin
Andi-Bogdan Postelnicu
Kristen Wright
Nathan Froyd
Junior Hsu
Tarek Ziadé
Razvan Maries
Dan Mosedale
Simon Fraser
Wander Lairson Costa
Edwin Takahashi
Rail Aliiev