Right now setup_perftest_test_date adds --test-date yesterday to all perftest
runs. we want that only for the ones doing batches
Differential Revision: https://phabricator.services.mozilla.com/D81562
Right now we are running `Coverity Static Analysis` for each merge to `mozilla-central`,
this is suboptimal since the resources required to do so are very expensive. It's
enough to run it once a day.
Differential Revision: https://phabricator.services.mozilla.com/D81510
Changes:
- add new flag in `web_platform_tests.py`, with name `backlog` that is a boolean value.
- simplify the timeout multiplier conditional to check for presence of the `backlog` flag.
- add the new flag to the `mozharness_extra_options` flag in `web-platform.yml`
Differential Revision: https://phabricator.services.mozilla.com/D81184
Changes:
- added tests that exercise manifest loading, mozinfo guessing and the overall process of chunking.
- tests added for both web-platform and traditional mochitest/xpcshell suites.
Differential Revision: https://phabricator.services.mozilla.com/D80985
And add suppressions for the new errors that this adds to the valgrind
run. It's not clear if it's a legitimate thing that LLVM does that
valgrind doesn't cope with, like many others, but the fact is running
valgrind on a PGO/LTO build doesn't show these errors, so we're not
actually shipping them anyways (but does show _different_ errors that we
don't see on the build the valgrind jobs do)
Differential Revision: https://phabricator.services.mozilla.com/D81016
Changes:
- install `xwit` package in the ubuntu1804 docker image setup phase.
- in `test-linux.sh` call xwit to reposition the cursor to a coodinate of 0,0
Differential Revision: https://phabricator.services.mozilla.com/D80698
Using a higher confidence threshold means manifest scheduling (i.e just |mach
try auto| for now), will schedule fewer manifests. We have data suggests that
this bump should reduce the number of manifests scheduled by more than half,
while only very slightly reducing the regression detection rate (still above
95%).
Differential Revision: https://phabricator.services.mozilla.com/D81085
There isn't a Debian package for that verson yet, so keep using the code
that pulls from the git repository, but use the revision that was
released as 3.16.1.
Differential Revision: https://phabricator.services.mozilla.com/D80957
We currently base this on the cb_name, but it would make be better to make this
explicit, so that different actions can share a permisssion. In particular, we are
adding a pair of new backfill actions that needs a singlle non-default permission.
Differential Revision: https://phabricator.services.mozilla.com/D80940
We are seeing a pretty broad distribution of results for the applink tests.
This bug increases the number of browsertime iterations from 10 to 14.
Differential Revision: https://phabricator.services.mozilla.com/D80363
Changes:
- change default return value for `get_runtimes` method to an empty dictionary if data is not found.
- add in fixtures and tests for `get_runtimes` and `chunk_manifests` method for web-platform-tests and subsuites.
Differential Revision: https://phabricator.services.mozilla.com/D80250
Changes:
- remove web-platform-tests from the test-set `macosx1014-tests`
- create new group `web-platform-tests-backlog` and move all backlog types into that group
- add the new group into test-platforms where applicable
Differential Revision: https://phabricator.services.mozilla.com/D80555
Changes:
Previous patch to apply the reduced timeout multiplier was only applicable to vanilla `web-platform-tests`. This patch reduces the chunk count for `web-platform-tests-reftest` and applies the reduction multiplier.
Differential Revision: https://phabricator.services.mozilla.com/D80520
This patch does a few small things to clean up our CI tests:
(1) The GPT cron is simplified so that it can be more manageable. In this change I also include a new helper method to make sure we run our android tests on the build variants that we should be running them on (and no others).
(2) The geckoview browsertime warm tests were running on 1 platform too many - this is no longer the case.
(3) Fennec vismet tests were previously excluded but are now included.
(4) All fennec tests that were in GPT cron have been moved to the Fennec_v68 cron so they only run once a week.
Differential Revision: https://phabricator.services.mozilla.com/D79891
It's required to properly setup psutil in the python3 virtualenv, and
psutil is required for build resources tracking by mach.
It's not clear to me why this hasn't been a problem since `mach build`
switched to python3, though. ¯\_(ツ)_/¯
Differential Revision: https://phabricator.services.mozilla.com/D80343
