ci: bound every unbounded CI job with timeout-minutes - #105
Merged
Conversation
Jobs without timeout-minutes fall back to GitHub's 360-minute default, so a hung runner burns six hours of Actions minutes before it is reaped. Bounds are derived from observed run durations and left deliberately loose: a timeout that fires under normal contention is worse than no timeout, because it turns a slow run into a phantom defect. Jobs that only call a reusable workflow (job-level `uses:`) are untouched -- they inherit their bound from the called workflow.
Contributor
Quality Report — ConductionNL/openbuild @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ✅ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| composer | ✅ | ✅ 100/100 | |||
| npm | ✅ | ✅ 662/662 | |||
| PHPUnit | ✅ | ||||
| Newman | ⏭️ | ||||
| Playwright | ⏭️ |
Coverage: 89.4% (17/19 statements)
Quality workflow — 2026-08-03 12:59 UTC
Download the full PDF report from the workflow artifacts.
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.
What
Adds
timeout-minutesto every CI job in this repo that was running unbounded.Why
A job without
timeout-minutesinherits GitHub's 360-minute default. A runner that hangs — a wedgednpm ci, a network stall, a container that never starts — burns six hours of Actions minutes before it is reaped, and the PR sits pending the whole time.How the values were picked
Bounds come from observed run durations across the fleet, not from guesses, and are left deliberately loose. A timeout that fires under normal contention is worse than no timeout, because it converts a slow run into a phantom defect.
pull-request-lint-check.yaml→lint-checkexporter-e2e.yml→exporter-e2eScope
Additions only, workflow files only. Job sets are unchanged — every touched file was re-parsed with
yaml.safe_loadand its job list compared against the base commit.Jobs that only call a reusable workflow (job-level
uses:) are intentionally untouched: they inherit their bound from the called workflow and GitHub does not honourtimeout-minuteson them.