Skip to content

ci(fast-checks): raise the every-run timeout to 45 min, state the budget as measured - #214

Merged
MaartenMarsman merged 1 commit into
developfrom
ci/fast-checks-timeout
Oct 21, 2026
Merged

MaartenMarsman merged 1 commit into
developfrom
ci/fast-checks-timeout

Conversation

@MaartenMarsman

Copy link
Copy Markdown
Collaborator

The ubuntu-latest runner slowed every test file by 1.4-2x between the August and October 2026 images (fast-checks runs 31265365814 and 39602904192; GitHub began migrating the label toward Ubuntu 26 on 2026-10-19). The every-run tier now takes 25 min of tests and the job has timed out at 30 min on every push since.

Changes:

  • fast-checks.yaml: timeout-minutes 30 -> 45; job name without the stale "~90 s"; header states the budget as the job's measured test phase.
  • helper-tiers.R, MAINTAINERS.md: the same budget statement; MAINTAINERS records the runner change.
  • nightly and weekly workflow headers: drop the stale "~90 s" line.

No test or package code changes. Verification: the T0 tier on develop at #211's head completed in 24.6 min of tests (8979 pass, 0 fail) one second before the 30-min cancel; this is the same run with room to finish.

…get as measured

The ubuntu-latest runner slowed every test file by 1.4-2x between the
August and October 2026 images (fast-checks runs 31265365814 and
39602904192). The every-run tier now takes 25 min of tests and the job
timed out at 30 min on every push. The budget statements in the
workflow, the tier helper and MAINTAINERS quote the job's measured test
phase instead of a fixed number.
@MaartenMarsman
MaartenMarsman merged commit 1e56803 into develop Oct 21, 2026
7 of 8 checks passed
@MaartenMarsman
MaartenMarsman deleted the ci/fast-checks-timeout branch October 21, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant