Repository navigation
ci: give web test shards headroom over their slowest run (10 → 15 minutes) - #637
Merged
Merged
Conversation
…utes) The slowest web shard takes about 10 minutes, setup and cleanup included (9m50s to 10m18s in October 2026). With a 10-minute cap, a shard whose every step passed was cancelled during cleanup, and the merge queue treated that as a failed check and ejected #634. The cap now keeps headroom over the slowest observed shard, as the server shards already do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
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 this changes
The time limit for the three Test Web jobs in
.github/workflows/ci.ymlgoes from 10 to 15 minutes. It's marked as a Scient change, since upstream uses 10.Why
The slowest web shard now takes about 10 minutes, setup and cleanup included (9 min 50 s to 10 min 18 s on recent runs). With a 10-minute limit, a shard can pass every step and still be cancelled during cleanup.
On #634's merge-queue run, Test Web 1 passed all its tests but was cancelled at 10 min 3 s. The queue counted the cancellation as a failed check and ejected the PR.
Times from that run:
15 minutes keeps roughly 50% headroom over the slowest observed shard, without padding far beyond it. The server shards already follow the same rule: their limit is 35 minutes, set because "a green shard gets cancelled mid-cleanup" otherwise.
Not done here: splitting the web tests into more shards would make them faster. But the shard names are required checks in branch protection, and the queue-reuse script expects three shards, so that's a separate decision.
🤖 Generated with Claude Code