ci: raise Test Workspace timeout to 75 minutes#189
Merged
Conversation
A cold rust-cache (every Cargo.lock change) means a full workspace + failpoints-feature build on the 2-core runner, which now exceeds 45 minutes on slow runner days — and because a timed-out run never saves its cache, an undersized budget self-perpetuates: every retry starts cold and dies identically (observed four consecutive 45-minute cancellations on main and PR #188 after #186's lock bump). Warm-cache runs stay ~15 minutes; 75 is headroom matching the rustfs job's budget, not a target. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
aaltshuler has reached the 50-review limit for trial accounts. To continue receiving code reviews, upgrade your plan.
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.
Unblocks #188 and main's own CI. Four consecutive 45-minute timeouts (main ×2, #188 ×2) since #186's
Cargo.lockbump: a coldrust-cachecosts a full workspace + failpoints-feature build on the 2-core runner, which exceeds 45 minutes on slow runner days — and a timed-out run never saves its cache, so the undersized budget self-perpetuates (every retry starts cold and dies the same way). Verified from the logs: zero failing tests; orphanedcargo/rustckilled mid-compile at the 45-minute mark.Warm-cache runs remain ~15 minutes — 75 is headroom (matching the RustFS job's budget), not a target. This PR's own run executes under the new budget and, on success, saves the new-lock cache that un-colds everything downstream.
🤖 Generated with Claude Code