ci(release): give quality checks thirty minutes on hosted runners - #104
Merged
Conversation
The release quality job runs the whole repository's check, typecheck, and test suites serially on one runner, the same work ci.yml spreads over four jobs. Blacksmith's 8 vCPU finished the Test step in 3m16s, so a 10-minute ceiling was fine. On the 4-vCPU GitHub-hosted runner that replaced it (#99) the Test step was still running at 7m44s when the ceiling cut the job, which GitHub reports as cancelled, and every publish job downstream skipped: the first nightly after the migration produced four successful platform builds and no release. Thirty minutes is roughly 2x the expected duration.
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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
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 Changed
release.yml: thequalityjob'stimeout-minutesgoes from 10 to 30, with a comment recording why.Why
The first nightly after the runner migration (#99), run
33004923066, built all four platforms successfully on hosted runners — macOS arm64 5.5 min, macOS x64 6.8 min, Windows 10.8 min, Linux 2.8 min — and then published nothing, becauseRelease quality checkshit its 10-minute ceiling (GitHub reports that as cancelled) and every publish job downstream skipped.That job runs
vp run testfor the whole repository serially on one runner — the same workci.ymlspreads over four jobs. Blacksmith's 8 vCPU did the Test step in 3m16s; the 4-vCPU hosted runner was still on it at 7m44s when it was cut. Expected total is around fifteen minutes, so thirty gives 2× headroom, in keeping withdocs/operations/release.md's "job timeouts are generous" rule (a ceiling costs nothing; a run killed at the limit wastes the whole matrix).Not changed: the job's shape. Sharding it like
ci.ymlwould cut wall time but adds four jobs to every release run; nightlies run every three hours and nothing waits on this job except publish.Checklist
Model: Claude Fable 5 · Harness: Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.