ci: give heavy-shard packages a 90-minute nextest test bound - #828
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #822. The 10-minute
terminate-aftercap was sized for the regular shards and killed legitimately long tests on the first genuinely-sharded run ofmain(run 31714159600):ruvector-mincut::subpolynomialtest_certify_cuts,test_delete_edge,test_incremental_updates— all TIMEOUT at exactly 600sruvector-nervous-system::retrieval_quality::pattern_separation_collision_rate— killed at 600sHistorical successful runs of those shards take up to ~75 minutes wall-clock with individual tests exceeding 10 minutes by design — the heavy shards exist to host them.
Fix: a
[[profile.default.overrides]]block scoped to the 13 packages of the two heavy shards withslow-timeout = { period = "300s", terminate-after = 18 }(90 min). A genuine hang in a heavy package now bounds at 1.5h instead of the 4h job budget; every other package keeps the 10-minute cap. Config validated locally withcargo-nextest show-config(exit 0).🤖 Generated with claude-flow