Skip to content

Reduce canary schedule frequency (AMD 4→2/day, ARM 8→2/day) #68821

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
potiuk wants to merge 1 commit into
base: main
Choose a base branch
from
+20 −10
Open

Reduce canary schedule frequency (AMD 4→2/day, ARM 8→2/day) #68821

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions .github/workflows/ci-amd.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,10 +26,11 @@
name: Tests (AMD)
on: # yamllint disable-line rule:truthy
schedule:
# Mirror of the previous AMD canary cron from before the AMD/ARM split (PR #66348),
# offset by 30 min from ARM's `:28` slot in `ci-arm.yml` so the two scheduled
# canaries don't compete for runners at exactly the same minute.
- cron: '58 1,7,13,19 * * *'
# AMD canary runs 2x/day (01:58, 13:58), interleaved with ARM's 2x/day (07:28, 19:28)
# in `ci-arm.yml` so a full-matrix canary still runs roughly every ~6h (alternating
# architecture) while halving the scheduled AMD compute. The `:58` vs ARM's `:28`
# offset keeps the two from competing for runners at exactly the same minute.
- cron: '58 1,13 * * *'
pull_request:
branches:
- main
Expand Down
6 changes: 5 additions & 1 deletion .github/workflows/ci-arm.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,11 @@
name: Tests (ARM)
on: # yamllint disable-line rule:truthy
schedule:
- cron: '28 1,3,7,9,13,15,19,21 * * *'
# ARM canary runs 2x/day (07:28, 19:28), interleaved with AMD's 2x/day (01:58, 13:58)
# in `ci-amd.yml` so a full-matrix canary still runs roughly every ~6h (alternating
# architecture). The `:28` vs AMD's `:58` offset keeps the two from competing for
# runners at exactly the same minute.
- cron: '28 7,19 * * *'
push:
# Post-merge pushes to release-prep / providers branches run on both
# AMD and ARM (the matching block lives in the other wrapper too —
Expand Down
15 changes: 10 additions & 5 deletions scripts/ci/prek/check_ci_workflows_in_sync.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,14 +107,19 @@
# file and must NOT appear in the other. The blocks are stripped before
# diffing so they don't show up as drift.
ARM_ONLY_BLOCK = """ schedule:
- cron: '28 1,3,7,9,13,15,19,21 * * *'
# ARM canary runs 2x/day (07:28, 19:28), interleaved with AMD's 2x/day (01:58, 13:58)
# in `ci-amd.yml` so a full-matrix canary still runs roughly every ~6h (alternating
# architecture). The `:28` vs AMD's `:58` offset keeps the two from competing for
# runners at exactly the same minute.
- cron: '28 7,19 * * *'
"""

AMD_ONLY_BLOCK = """ schedule:
# Mirror of the previous AMD canary cron from before the AMD/ARM split (PR #66348),
# offset by 30 min from ARM's `:28` slot in `ci-arm.yml` so the two scheduled
# canaries don't compete for runners at exactly the same minute.
- cron: '58 1,7,13,19 * * *'
# AMD canary runs 2x/day (01:58, 13:58), interleaved with ARM's 2x/day (07:28, 19:28)
# in `ci-arm.yml` so a full-matrix canary still runs roughly every ~6h (alternating
# architecture) while halving the scheduled AMD compute. The `:58` vs ARM's `:28`
# offset keeps the two from competing for runners at exactly the same minute.
- cron: '58 1,13 * * *'
pull_request:
branches:
- main
Expand Down
Loading