Skip to content

ci: give the test job headroom over its runtime - #63

Merged
roughcoder merged 1 commit into
mainfrom
ci/raise-test-timeout
Aug 20, 2026
Merged

roughcoder merged 1 commit into
mainfrom
ci/raise-test-timeout

Conversation

@roughcoder

@roughcoder roughcoder commented Aug 20, 2026 •

Copy link
Copy Markdown

The Test job runs ~9m30s against a timeout-minutes: 10 cap, so it sits at ~95% of its budget on a good day and ordinary runner variance cancels healthy runs.

PR #61 lost one at 10m02s: the Test step itself had already passed and the job was killed during post-job cleanup. The identical rerun, with nothing changed, passed at 9m21s. Recent runs on main show the same squeeze — 7m56s, 9m24s, 9m34s — with cancelled runs already in the history.

Raises the Test job to 12 minutes.

The other three jobs keep their 10m cap deliberately: Check runs ~3m, Release Smoke ~1m, and the mobile job is parked behind if: false. A cap those never approach is still doing its real job of catching a hang, and raising it everywhere would just slow down detection.

The inline comment notes that this should be raised alongside genuine suite growth rather than used to paper over a regression in it.

Produced by Claude Fable 5 via Claude Code.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

The suite runs ~9m30s against a 10m cap, so ordinary runner variance
cancelled healthy runs. PR #61 lost one at 10m02s with every test
already passed, killed during post-job cleanup, and the identical rerun
passed at 9m21s.

Raises the test job to 12 minutes. The other jobs keep their 10m cap:
Check runs ~3m and Release Smoke ~1m, and a cap they never approach is
still doing its job of catching a hang.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@roughcoder
roughcoder merged commit d6a3cd0 into main Aug 20, 2026
8 checks passed
@roughcoder
roughcoder deleted the ci/raise-test-timeout branch August 20, 2026 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant