This removes the no-longer-supported Node8 stuff from the taskcluster configuration and the repack script.
Depends on D62782
Differential Revision: https://phabricator.services.mozilla.com/D62783
--HG--
extra : moz-landing-system : lando
Depends on D62781, which upgrades NodeJS to 10.19.0. This patch merely changes the -node aliases so that we now default to Node 10.
Differential Revision: https://phabricator.services.mozilla.com/D62782
--HG--
extra : moz-landing-system : lando
NodeJS 8.x is End-of-Lifed and is no longer receiving security fixes. 10.19.0 is now the oldest Long Term Support version of NodeJS, and it has just been released with several HTTP security fixes.
Differential Revision: https://phabricator.services.mozilla.com/D62781
--HG--
extra : moz-landing-system : lando
This patch adds a v80 chromedriver for chrome. It also removes old chromedrivers (v76, and v77) from the fetch tasks.
Differential Revision: https://phabricator.services.mozilla.com/D62897
--HG--
extra : moz-landing-system : lando
As opposed to what was intended, the directories weren't eliminated
correctly.
Differential Revision: https://phabricator.services.mozilla.com/D62700
--HG--
extra : moz-landing-system : lando
Provides denylisted attributes to copy over in the fusing of chunked portions of the taskgraph. Without
denylisting these we have changes on these related kinds in json, due simply to ordering of total tasks.
Differential Revision: https://phabricator.services.mozilla.com/D62637
--HG--
extra : moz-landing-system : lando
GCE instances use Ubuntu 18.04, which is known to cause issues in
valgrind builds (Bug 1545094), while EC2 uses Ubuntu 14.04.
Move valgrind builds back to GCE to avoid perma fail of these jobs.
Differential Revision: https://phabricator.services.mozilla.com/D62552
--HG--
extra : moz-landing-system : lando
In GCP we have the double the number of core compared to AWS
counterparts, but we use the same amount of memory. Request the builds
to be less parallel to avoid OOM.
Differential Revision: https://phabricator.services.mozilla.com//D62514
Accepting an argument to specify a tarball of browsertime results was an
artifact of the previous split between the (now removed) visual-metrics and
visual-metrics-dep job kinds. Now that we are always providing the browsertime
results as a fetch task, can retrieve it directly from `MOZ_FETCHES` directory.
Differential Revision: https://phabricator.services.mozilla.com/D62364
--HG--
extra : moz-landing-system : lando
Raptor was previously generating two artifacts for the `run-visual-metrics.py`
script to consume: `jobs.json` and `application.json`. These artifacts have
been merged.
Differential Revision: https://phabricator.services.mozilla.com/D62363
--HG--
extra : moz-landing-system : lando
In bug 1601414, the JSON parsing and validating code was refactored into a
single method. However, the `return 1` in case of error was carried over. That
was correct in the previous version because that 1 was being passed to `exit()`
later on. However, we were now returning 1 to callers of `read_json` when the
schema did not match, resulting in an opaque unrelated error (`TypeError: 'int'
object is not subscriptable`).
Now `read_json` is correctly raising an exception so its callers know when it
fails.
Differential Revision: https://phabricator.services.mozilla.com/D62361
--HG--
extra : moz-landing-system : lando
The `extraOptions` key in the Perfherder output was only required until Bug
1593198 landed.
Differential Revision: https://phabricator.services.mozilla.com/D62360
--HG--
extra : moz-landing-system : lando
The `run-visual-metrics.py` script was intended to consume a `jobs.json` file
containing one `browsertime.json` per video. However it was not being used as
such and was continuously re-processing the first video specified in the
`browsertime.json` file. If a job were submitted with a `browsertime.json`
containing 15 videos and 15 different videos, only the first would be
processed. This leads to us having incorrect metrics because over all runs all
the metrics will be identical.
Now we only specify the `browsertime.json` in the `jobs.json` file and extract
the paths to videos from there. Also because we are never downloading inputs
this way, we get to remove some dead code and our dependency on `requests`.
Differential Revision: https://phabricator.services.mozilla.com/D62320
--HG--
extra : moz-landing-system : lando
We are migrating the worker used by builds from AWS to GCP. We have had tier- 3 GCP builds for initial testing. We are replacing those with tier-3 AWS builds to ensure they keep working so we are able to switch back.
Differential Revision: https://phabricator.services.mozilla.com/D60042
--HG--
extra : moz-landing-system : lando
I need this to support individual #[cfg] in enum variants, which is used for
Image::PaintWorklet.
Differential Revision: https://phabricator.services.mozilla.com/D62160
--HG--
extra : moz-landing-system : lando