ci: add per-job timeout backstops - #34
Merged
Merged
Conversation
Cap every CI job (10min, 15 for the Playwright browser job) and the release job (25min) so a wedged step can't pin a runner until GitHub's ~6h default. Mirrors the timeout-minutes backstop used in the dim0 Tests workflow.
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 free
to 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.
Context
The repo already runs tests on every push/PR to
main(ci.yml: lint-typecheck, unit, browser, build) and already gates the manualrelease.ymlon the full suite + browser tests. So no new workflow is needed.The one gap vs. our other repos (
vcmf/dim0'stests.yml) was no job timeouts — a wedged step (most likely a hung Playwright/chromium page) could hold a runner until GitHub's ~6h default.Change
Adds
timeout-minutesbackstops only:ci.yml: lint-typecheck / test-unit / build = 10min, test-browser = 15minrelease.yml: release job = 25min (full suite + browser + rebuild + npm publish)Generous vs. actual run times; purely a safety net. No behavioral change to what runs.
Deliberately not adopted
format:checkstep —pnpm lint(biome check .) already asserts formatting.