fix(release): shard server tests out of the quality job - #88
Merged
Conversation
"Release quality checks" runs check, typecheck, and the full test suite in one job with a 10-minute limit. The job has sat at that limit for weeks and timed out on the last three releases while every test was passing, which marks the whole run cancelled even when the release publishes. Move apps/server tests into a three-shard `quality_server` job, the same split ci.yml uses, and leave the remaining packages in `quality`. Server tests run one file at a time, so sharding them across runners is what actually shortens the wall clock. Made with Claude Fable 5.1 in Claude Code.
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.
Problem
"Release quality checks" runs check, typecheck, and the whole test suite in one job with a 10-minute limit. Durations over the last eight release runs sat between 8m28s and 10m17s, and the last three all hit the limit while every test was passing. The timeout marks the whole run cancelled even when the release publishes, which is why several recent Release runs read as cancelled despite shipping.
The fork runs this job on GitHub-hosted
ubuntu-24.04rather than upstream's 8-vCPU Blacksmith runner, and the suite has grown since.Fix
Move
apps/servertests into a three-shardquality_serverjob and leave the remaining packages inquality, the same splitci.ymlalready uses. Server tests run one file at a time (fileParallelism: false), so spreading them across runners is what actually shortens the wall clock. From the Sep 10 log,qualityshould now finish in about 7 to 8 minutes and each shard in 3 to 4.Gating is unchanged: the publish job did not depend on
qualitybefore and still does not.Verification
Workflow parses as valid YAML and passes the formatter. The Release run triggered by merging this shows the real timings.
Made with Claude Fable 5.1 in Claude Code.