From 12e8aa3ebc73c2b5b1bee4d11c5045087d6b70b0 Mon Sep 17 00:00:00 2001 From: ruvnet Date: Mon, 4 May 2026 05:05:54 -0400 Subject: [PATCH] =?UTF-8?q?ci(workspace):=20bump=20core-and-rest=20timeout?= =?UTF-8?q?=20150=E2=86=92180min=20(iter=20231)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit iter-230's exclusion of the 4 hailo crates from the catch-all shard was necessary but not sufficient. Historical successful runs of `Tests (core-and-rest)` landed at 2h 30m 16s — exactly at the old 150min cap with no headroom. Two PR-413 runs (iter 228 on 9db4499a7, iter 230 on a58bdd061) both got cancelled mid-test when the shard's natural runtime drifted past the cap. Bumping to 180min gives ~30min headroom on the typical run. If a future regression pushes the shard past 180min we should split crates out into a sibling shard (the way ml-research-heavy and core-and-rest-heavy were carved out at iters 122/128) rather than keep raising this cap. Same iter-pattern as iter-228 + iter-229 + iter-230: each iter-219 workspace-rejoin side effect surfaces under a different CI matrix configuration and gets fixed in turn. Failing job: Tests (core-and-rest) on PR #413 (a58bdd061): completed cancelled — 150min cap hit at step #7 Tests (core-and-rest) on PR #413 (9db4499a7): completed cancelled — same cap Co-Authored-By: claude-flow --- .github/workflows/ci.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 8e3f5573..a28d40f7 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -79,7 +79,15 @@ jobs: # `core-and-rest` is the catch-all shard and compiles ~50 crates; on a # cold cache the build alone has hit ~90min, so headroom matters more # than tight feedback for this job. Faster shards still finish in ~10–20m. - timeout-minutes: 150 + # Iter 231 — bumped 150→180. Historical successful runs landed at + # 2h 30m 16s (just under the old cap); two PR-413 runs (iter 228 + + # iter 230) both hit the cap and got cancelled mid-test. Excluding + # the iter-219 hailo crates from the catch-all (iter 230) was a + # necessary but not sufficient fix — the shard was already at the + # ragged edge. 180min gives ~30min headroom on the typical 150min + # run; if a shard's natural duration drifts further we should split + # crates out into a new sibling shard rather than push this higher. + timeout-minutes: 180 strategy: fail-fast: false matrix: