Uh oh!
There was an error while loading. Please reload this page.
[v3-3-test] Reduce canary schedule frequency (AMD 4->2/day, ARM 8->2/day) (#68821) - #69039
Merged
Conversation
…day) (#68821) The scheduled canary runs the full matrix on all versions and is by far the most expensive run type. AMD ran 4x/day and ARM 8x/day; halving AMD alone saves ~1,900 compute-h / 2 weeks (~6% of AMD CI), and cutting ARM 8->2/day removes 75% of the ARM canary schedule. The two crons are interleaved (AMD 01:58 & 13:58, ARM 07:28 & 19:28) so a full-matrix canary still runs roughly every ~6h, alternating architecture - so the 'trust earned on main' backstop keeps a ~6h effective cadence for arch-agnostic regressions (12h for arch-specific ones) while the scheduled compute drops substantially. It also relieves runner-pool queuing, since each canary is the heaviest job-flood. check_ci_workflows_in_sync.py expected blocks updated to match. (cherry picked from commit 5226a1b) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
1 task
potiuk
marked this pull request as ready for review
June 26, 2026 18:52
potiuk
requested review from
amoghrajesh, ashb, bugraoz93, gopidesupavan, jason810496, jscheffl and potiuk
as code ownersJune 26, 2026 18:52
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The scheduled canary runs the full matrix on all versions and is by far the most
expensive run type. AMD ran 4x/day and ARM 8x/day; halving AMD alone saves
~1,900 compute-h / 2 weeks (~6% of AMD CI), and cutting ARM 8->2/day removes 75%
of the ARM canary schedule.
The two crons are interleaved (AMD 01:58 & 13:58, ARM 07:28 & 19:28) so a
full-matrix canary still runs roughly every ~6h, alternating architecture - so
the 'trust earned on main' backstop keeps a ~6h effective cadence for
arch-agnostic regressions (12h for arch-specific ones) while the scheduled
compute drops substantially. It also relieves runner-pool queuing, since each
canary is the heaviest job-flood.
check_ci_workflows_in_sync.py expected blocks updated to match.
(cherry picked from commit 5226a1b)
Co-authored-by: Jarek Potiuk jarek@potiuk.com