Chrome responsiveness test have been running every Monday, Wednesday, and Friday on the general_perf_testing cron
We have been exeriencing issues with these tests, and this patches disables their running on the GPT cron
Differential Revision: https://phabricator.services.mozilla.com/D211279
As part of our okr goals of being competative in pageload we are running essential pageload tests on chrome on android to have an idea of how we compare to chrome on android
Differential Revision: https://phabricator.services.mozilla.com/D209981
When running `mach try fuzzy` locally, notarization jobs end up in the
full graph, because level isn't forced to 1. As part of try's decision
task though, they're filtered out in the mac_notarization transforms.
Adding them to UNCOMMON_TRY_TASK_LABELS means they won't be selected
at least in the non-`--full` case.
Differential Revision: https://phabricator.services.mozilla.com/D205693
As chromium is no longer used and chromium as release is replacing it, we are removing all references to it to not confuse people
Differential Revision: https://phabricator.services.mozilla.com/D204821
In bug 1882100 I updated the nightly-android method to include
ship-geckoview, but in bug 1882083 I'd picked the wrong function to
select android tasks as part of nightly-all, so geckoview ship tasks
went missing.
Remove the duplicate/confusing target_tasks_nightly from
android_taskgraph to prevent something like this happening again.
Differential Revision: https://phabricator.services.mozilla.com/D205330
This patch removes the windows 10 reference hardware talos tests, and removes the platform config for it. With talos tests disabled on the windows10 reference hardware, we can also remove any configuration steps that we have for that platform since there are no other tests running on those machines.
Differential Revision: https://phabricator.services.mozilla.com/D205080
This patch enables motionmark 1.3 on Chrome in CI for the A51 devices as
it was previously on all other apps except for `chrome-m`
Differential Revision: https://phabricator.services.mozilla.com/D204820
This patch removes the windows 10 reference hardware talos tests, and removes the platform config for it. With talos tests disabled on the windows10 reference hardware, we can also remove any configuration steps that we have for that platform since there are no other tests running on those machines.
Differential Revision: https://phabricator.services.mozilla.com/D205080
This patch sets up the scheduling for fenix performance tests on mozilla-central, and autoland. All the same tests will be running across both branches. However, the youtube-playback tests will only be running on mozilla-central. It also removes fenix speedometer tests from the gpt cron since they'll be running on every commit.
Differential Revision: https://phabricator.services.mozilla.com/D202872
This typically shouldn't happen because both the try push and Decision task are
generating the graph based off the same revision. But one scenario it's
possible is if the local graph was loaded from cache and there are invalidation
bugs.
A known invalidation bug can happen when a variant expires in-between when a
cached graph was saved and loaded.
Differential Revision: https://phabricator.services.mozilla.com/D203282
We are adding the ability to run chrome, fenix and custom-car regularly on mozilla central
We need data from the new android devices for speedometer3, so we are temporarily adding the ability to run custom-car, chrome-m and fenix on the new generation of devices we want to test on.
Only speedometer3 for now as that is all we have capacity for at the moment
Differential Revision: https://phabricator.services.mozilla.com/D202867
During the enabling of safaridriver we ran into user permission issues and as a result were unable to enable run safari tests on M2s
The issue we were encountering was `kernel: (Sandbox) Sandbox: com.apple.WebDriver.HTTPService(30714) deny(1) network-bind local:*:7055`.
This issue was precenting from webdriver from starting and the permission issue was caused by running a taskcluster-worker as system daemon vs. a per-user launch agent.
The issue was specific to OSX 13, and so it was decided to upgrade the machines from OSX 13 to OSX 14 to resolve the issue and give us a more modern OS to test speedometer against in general
Differential Revision: https://phabricator.services.mozilla.com/D202503
This patch reduces the number of tasks run on-push on the pine project branch: Specifically, if stops running reftests and web-platform tests, as discussed with :bytesized.
There is an existing task filter for pine, but it isn't enabled and hasn't been in use for some time: pine currently runs all the normal mozilla-central tasks.
Most active project branches use a task filter to reduce task costs and load. pine doesn't seem to have frequent pushes, so this hasn't been a big consideration, but I think any reduction in unneeded tasks can only be helpful.
Differential Revision: https://phabricator.services.mozilla.com/D201648
This patch runs talos/awsy tests on the beta/release branches with a cron instead of on every commit. Some additional changes are made to the existing crons for this to work.
Differential Revision: https://phabricator.services.mozilla.com/D201279
This patch modifies the weekly release, and daily beta crons to run the browsertime desktop tests. The crons will also be scheduled at a different time now to be more in line with commits that run tests. At the same time, some of the other crons are modified to use a single method for checking if a platform is a desktop platform that can have tests running on it (similar to what we do for android).
Differential Revision: https://phabricator.services.mozilla.com/D201250
As a part of our performance strategy we are expanding the devices we run performance tests on
In this patch we are adding the S21 taskcluster definitions and the ability to run speedometer and speedometer3 on those devices
Differential Revision: https://phabricator.services.mozilla.com/D198721
