mirror of
https://github.com/ruvnet/RuVector.git
synced 2026-05-23 12:55:26 +00:00
ci(workspace): bump core-and-rest timeout 150→180min (iter 231)
Some checks failed
ruvector-verified CI / bench (push) Has been cancelled
ruvector-verified CI / check (--features hnsw-proofs) (push) Has been cancelled
ruvector-verified CI / check (--features rvf-proofs) (push) Has been cancelled
ruvector-verified CI / check (--features serde) (push) Has been cancelled
ruvector-verified CI / check (--features ultra) (push) Has been cancelled
ruvector-verified CI / clippy (push) Has been cancelled
ruvector-verified CI / check () (push) Has been cancelled
ruvector-verified CI / check (--all-features) (push) Has been cancelled
ruvector-verified CI / check (--features all-proofs) (push) Has been cancelled
ruvector-verified CI / check (--features coherence-proofs) (push) Has been cancelled
hailo-backend audit / cargo-audit (cluster) (push) Has been cancelled
hailo-backend audit / clippy --all-targets -D warnings (cluster) (push) Has been cancelled
hailo-backend audit / cargo-deny (license + bans + sources) (push) Has been cancelled
hailo-backend audit / test (cluster — lib + integration + cli + doctest) (push) Has been cancelled
hailo-backend audit / missing-docs check (push) Has been cancelled
hailo-backend audit / cross-build aarch64 (all bridges) (push) Has been cancelled
ruvector-verified CI / test (push) Has been cancelled
Some checks failed
ruvector-verified CI / bench (push) Has been cancelled
ruvector-verified CI / check (--features hnsw-proofs) (push) Has been cancelled
ruvector-verified CI / check (--features rvf-proofs) (push) Has been cancelled
ruvector-verified CI / check (--features serde) (push) Has been cancelled
ruvector-verified CI / check (--features ultra) (push) Has been cancelled
ruvector-verified CI / clippy (push) Has been cancelled
ruvector-verified CI / check () (push) Has been cancelled
ruvector-verified CI / check (--all-features) (push) Has been cancelled
ruvector-verified CI / check (--features all-proofs) (push) Has been cancelled
ruvector-verified CI / check (--features coherence-proofs) (push) Has been cancelled
hailo-backend audit / cargo-audit (cluster) (push) Has been cancelled
hailo-backend audit / clippy --all-targets -D warnings (cluster) (push) Has been cancelled
hailo-backend audit / cargo-deny (license + bans + sources) (push) Has been cancelled
hailo-backend audit / test (cluster — lib + integration + cli + doctest) (push) Has been cancelled
hailo-backend audit / missing-docs check (push) Has been cancelled
hailo-backend audit / cross-build aarch64 (all bridges) (push) Has been cancelled
ruvector-verified CI / test (push) Has been cancelled
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 on9db4499a7, iter 230 ona58bdd061) 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 <ruv@ruv.net>
This commit is contained in:
parent
a58bdd0614
commit
12e8aa3ebc
1 changed files with 9 additions and 1 deletions
10
.github/workflows/ci.yml
vendored
10
.github/workflows/ci.yml
vendored
|
|
@ -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:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue