ruvector

mirror of https://github.com/ruvnet/RuVector.git synced 2026-08-20 22:23:49 +00:00

History

ruv 784aa56749 ci: give heavy-shard packages a 90-minute nextest test bound The terminate-after cap added in #822 (10 minutes) was sized for the regular shards and killed legitimately long tests on the first sharded run of main: ruvector-mincut subpolynomial tests and ruvector-nervous-system pattern_separation_collision_rate all TIMEOUT at exactly 600s in run 31714159600, failing ml-research-heavy and core-and-rest-heavy. Historical successful runs of those shards take up to ~75 minutes with individual tests exceeding 10 minutes by design. Scope a slow-timeout override to the 13 packages of the two heavy shards: 300s SLOW reporting period, killed after 18 periods (90 min) — still bounding a genuine hang at 1.5h instead of the 4h job budget. Co-Authored-By: claude-flow <ruv@ruv.net>	2026-08-13 11:55:45 -04:00
..
nextest.toml	ci: give heavy-shard packages a 90-minute nextest test bound	2026-08-13 11:55:45 -04:00

ruv 784aa56749 ci: give heavy-shard packages a 90-minute nextest test bound

The terminate-after cap added in #822 (10 minutes) was sized for the
regular shards and killed legitimately long tests on the first sharded
run of main: ruvector-mincut subpolynomial tests and
ruvector-nervous-system pattern_separation_collision_rate all TIMEOUT
at exactly 600s in run 31714159600, failing ml-research-heavy and
core-and-rest-heavy. Historical successful runs of those shards take
up to ~75 minutes with individual tests exceeding 10 minutes by design.

Scope a slow-timeout override to the 13 packages of the two heavy
shards: 300s SLOW reporting period, killed after 18 periods (90 min) —
still bounding a genuine hang at 1.5h instead of the 4h job budget.

Co-Authored-By: claude-flow <ruv@ruv.net>

2026-08-13 11:55:45 -04:00

nextest.toml

ci: give heavy-shard packages a 90-minute nextest test bound

2026-08-13 11:55:45 -04:00