Changes:
Add a new configuration file for GDM that forces the use of X11 instead of Wayland.
This may help with reducing the number of crashes due to window managers.
Differential Revision: https://phabricator.services.mozilla.com/D67006
--HG--
extra : moz-landing-system : lando
Changes:
As documented in bug 1621483, `marionette` experiences a non-trivial amount of issues when run on ubuntu1804 docker image with GTK/GNOME desktop environment enabled.
GTK/GNOME has a higher degree of asynciness when manipulating window size/position and this leads to `marionette` and the derived suite `web-platform-tests-wdspec` reporting intermittent oranges for a number of tests.
While attempts were made to incorporate a fix for the marionette driver itself, the best attempts have only been able to achieve a ~50% reliability in green runs.
This patch reintroduces the use of bare `compiz` window manager exclusively for these two problematic test suites so that at least the tests are running on non-legacy software.
Differential Revision: https://phabricator.services.mozilla.com/D66482
--HG--
extra : moz-landing-system : lando
Add filename support for plain display
Update fzf version in tests
Update tooltool url for fzf
Differential Revision: https://phabricator.services.mozilla.com/D66571
--HG--
extra : moz-landing-system : lando
Creating the virtualenv prints an error message in the diffoscope docker
image because it doesn't have a compiler or the python development
headers, and that triggers an error setting up psutil after bug 1620513,
which in turn leads to a noisy and unrelated error message appearing in
the diffoscope jobs when they fail.
We don't need psutil set up really in those jobs, let alone a full
fledged virtualenv, so we can avoid the psutil error message by
disabling the virtualenv.
Differential Revision: https://phabricator.services.mozilla.com/D66361
--HG--
extra : moz-landing-system : lando
Changes:
Remove the unnecessary setup phase of `valgrind` on the docker image, given that we are not scheduling `mochitest-valgrind` [anywhere](https://searchfox.org/mozilla-central/source/taskcluster/ci/test/mochitest.yml#300) in the CI system.
Also, clean up `test-sets.yml` by renaming the `linux-common-tests` to `linux1604-legacy-tests` to better reflect that the set holds tests that haven't been migrated over to linux1804 yet.
Differential Revision: https://phabricator.services.mozilla.com/D65832
--HG--
extra : moz-landing-system : lando
Adjust runme to be executable
Rm sdk/pltf install.Manually add meta
Enforce firefox run instead of notify
Add policy to disable updates
Temp hack to default to firefox instead of notify-send
Fix mach linters
Remove firefox command hack. Proper fix
Remove duplicate cmd in runme
Fix indentantion in kind
Fix more linters
Differential Revision: https://phabricator.services.mozilla.com/D59561
--HG--
extra : moz-landing-system : lando
Changes:
Pin the source docker image to a specific tag from canonical.
Remove unneeded packages that are either installed as part of the setup, or come preinstalled.
Silence the `dbus` startup message by redirecting the output to `2&>1`.
Remove unnecessary `locale-gen` call at the end of setup.
Differential Revision: https://phabricator.services.mozilla.com/D65434
--HG--
extra : moz-landing-system : lando
Changes to the firefox-snap Docker image to support building Thunderbird Snap
packages as well.
Replaced hardcoded "firefox" instances in runme.sh with $PRODUCT variable and
renamed "snapcraft.yaml.in" to "firefox.snapcraft.yaml.in".
Differential Revision: https://phabricator.services.mozilla.com/D63035
--HG--
rename : taskcluster/docker/firefox-snap/snapcraft.yaml.in => taskcluster/docker/firefox-snap/firefox.snapcraft.yaml.in
extra : moz-landing-system : lando
backports.lzma couldn't cleanly be installed because we were now using Python3.8 but hadn't specified that in the Pipfile. Also took the opportunity to remove the pip version restriction which is no longer needed.
Differential Revision: https://phabricator.services.mozilla.com/D63892
--HG--
extra : moz-landing-system : lando
backports.lzma couldn't cleanly be installed because we were now using Python3.8 but hadn't specified that in the Pipfile. Also took the opportunity to remove the pip version restriction which is no longer needed.
Differential Revision: https://phabricator.services.mozilla.com/D63892
--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
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
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
Changes:
Since the image `debian10-test` is not being used to run unittests on CI, a lot of the dependencies installed can be removed.
Differential Revision: https://phabricator.services.mozilla.com/D60945
--HG--
extra : moz-landing-system : lando