ci: raise Test Workspace timeout to 75 minutes

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>
This commit is contained in:
aaltshuler 2026-06-11 10:38:54 +03:00
parent 1b1583d897
commit 7f32e6f1bc

View file

@ -127,7 +127,13 @@ jobs:
name: Test Workspace
needs: classify_changes
runs-on: ubuntu-latest
timeout-minutes: 45
# 75, not 45: a cold rust-cache (every Cargo.lock change) costs a full
# workspace + failpoints-feature build on a 2-core runner, which now
# exceeds 45 minutes on slow runner days. A timed-out run never SAVES
# its cache, so an undersized budget self-perpetuates: every retry
# starts cold and dies the same way (observed 2026-06-11, four runs).
# Warm-cache runs stay ~15 minutes; this is headroom, not a target.
timeout-minutes: 75
permissions:
contents: write
env: