From 7f32e6f1bc092a3e2a3d87ec354551f3f61c9ddc Mon Sep 17 00:00:00 2001 From: aaltshuler Date: Thu, 11 Jun 2026 10:38:54 +0300 Subject: [PATCH] ci: raise Test Workspace timeout to 75 minutes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- .github/workflows/ci.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 15e6d11..a77108f 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -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: