Skip to content

feat(schedules): stagger nongnu and gnu-alpha off gnu's slots - #10

Closed
jshvn wants to merge 1 commit into
mainfrom
josh/stagger-gnu
Closed

jshvn wants to merge 1 commit into
mainfrom
josh/stagger-gnu

Conversation

@jshvn

@jshvn jshvn commented Oct 9, 2026

Copy link
Copy Markdown
Member

gnu, nongnu and gnu-alpha all start at 03:42 and 15:42 UTC. This change gives each one its own slots:

Job Slots UTC
gnu S3 | S15 03:42, 15:42 (no change)
nongnu S7 | S19 07:42, 19:42
gnu-alpha S9 | S21 09:42, 21:42

The two mirrors that read ftp.gnu.org are six hours apart. No slot is shared with tlnet, dropbox or github. A run takes 1 to 3 minutes, and up to 11 minutes with reconcile.

On the first tick after the deploy, each moved job fires one time for its latest new slot if that slot is after the slot that the state records. Between 03:42 and the first new slot, the tick logs a "clock behind" warning for the moved jobs and does not fire them. This is not an error.

The healthchecks.io crons of nongnu and gnu-alpha must change with this deploy: 42 7,19 * * * and 42 9,21 * * * UTC.

Test plan:

  • task check (gofmt, vet, tests)
  • task targets lists nongnu at 07:42, 19:42 and gnu-alpha at 09:42, 21:42

gnu, nongnu and gnu-alpha all started at 03:42 and 15:42 UTC. nongnu moves to
07:42 and 19:42 (S7 | S19), gnu-alpha to 09:42 and 21:42 (S9 | S21). gnu stays.
The two mirrors that read ftp.gnu.org are six hours apart. No slot is shared with
tlnet, dropbox or github.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant