We were using and removing flathub-scope from the job for production
releases, but on staging/try it was staying around causing a schema
validation error later on.
Differential Revision: https://phabricator.services.mozilla.com/D195634
This patch fixes an issue in the add-all-browsertime task to prevent it from running tasks that aren't defined to run on the project it was requested from. For example, on autoland, this has the effect of preventing tests that don't have autoland specified in their run-on-projects setting from being selected.
Differential Revision: https://phabricator.services.mozilla.com/D195256
`fetch_graph_and_labels` grabs the `label_to_taskid` mapping from the original
decision task plus any action and cron tasks on the same revision. In that
process it only keeps track of one task id per label (whichever it sees last).
In most cases that's not a big deal, but there's a couple of instances where it
matters:
- the `rerun` action checks that the input task id is part of the mapping, and
doesn't do anything if it is not, so won't rerun a task that was part of the
initial graph and whose label was re-used later (e.g. from a retrigger)
- the `retrigger-multiple` action checks to see if a label should be rerun
instead, and in that case uses the label_to_taskid mapping to decide which
exact task to rerun. Again if there's more than one task on that revision
with the same label (e.g. from a forced retrigger or cron), it might not pick
the expected one.
Fix this by having `fetch_graph_and_labels` also return a `label_to_taskids`
mapping. The `rerun` action's check now looks for the task id there instead of
the incomplete `label_to_taskid`, and `retrigger-multiple` attempts to rerun
all tasks with the given label instead of just one.
Differential Revision: https://phabricator.services.mozilla.com/D194600
Update the chrommium fetch cron to now include the ARM64 Mac OS relevant
files. This ensures we will have available the correct chromedriver for
CaR on Apple Silicon.
Differential Revision: https://phabricator.services.mozilla.com/D193865
This patch updates the chromium fetches to now include the ARM builds so
that we can use the appropriate chromedriver for CaR apple silicon
(arm64) builds.
Differential Revision: https://phabricator.services.mozilla.com/D192943
Getting this to run on Try through fuzzy or other selectors means we either need to remove or get past the `run-on-releases` selector used by this job. The former is not ideal, as it causes the job to begin to run on beta and other releases (which will probably just end up failing), so I'm adjusting `release_type` on Try to be set to Nightly.
Based on what I see `release_type` being used for, and what `run-on-releases` is set to, I believe this shouldn't have impacts outside of what I intend...but it's difficult to be absolutely certain of that. In any case, there is virtually zero chance that this could bust anything outside of Try.
Differential Revision: https://phabricator.services.mozilla.com/D192262
We were experincing an issue of chrome on M2 chips taking 5-7 times longer than firefox on M2 chips
After debugging it was discovered the chrome universal binary was runnning x86 with rosetta
The chromedriver version was arm, but the node process running the chromedriver was x86
This patch changes node to run as arm not x86, which looks to have slipped through the inital setup of the M2s
Differential Revision: https://phabricator.services.mozilla.com/D194532
This patch adds a transform that applies the backstop optimization strategy to all perftest tasks. At the same time, the tier for all perftest tasks is limited here to tier 2, and 3. We shouldn't have any tier 1 tasks running at this stage.
Differential Revision: https://phabricator.services.mozilla.com/D194378
This patch modifies the target tasks so that we don't run the sp3 tests
more than once a day for the Android custom-CaR application. This is for
consistency as this is already taken care of in the
`custom-car_perf_testing` which handles custom-car for all platforms.
Differential Revision: https://phabricator.services.mozilla.com/D192518
This does the plumbing work for adding jobs here. a few things remain:
1) getting the resolution to be ideal on the machines, right now it
fails to adjust
2) getthing the mda-gpu job green
3) setting the branches to run on for mda-gpu hw-ref
Differential Revision: https://phabricator.services.mozilla.com/D192681
Removes the direct relationship between hardened-signing type (production/developer) and project/release level. Having them separate should make it more explicit on when to use production entitlements or not.
Differential Revision: https://phabricator.services.mozilla.com/D191705
There's no reason we need to back out all of the attribution job changes - we can just pull the dmgs directly from `repackage` instead.
Differential Revision: https://phabricator.services.mozilla.com/D192599
