ci: move rivet-core mutation matrix to nightly so it stops saturating runners (#498)#504
Merged
Conversation
… runners (#498) The 16-shard rivet-core mutation matrix is non-gating (continue-on-error) but runner-heavy: 16 shards x 45min on the self-hosted lean-mem pool. On every push it saturated the pool, queueing the actual gating jobs (test, clippy, mutants-cli) behind it for hours (#498). Split the mutation work: - mutants-core (rivet-core, 16 shards): now NIGHTLY + manual only via `if: github.event_name == 'schedule' || workflow_dispatch`, with a new `schedule: cron '0 3 * * *'` + `workflow_dispatch:` trigger. Stays non-gating. - mutants-cli (rivet-cli, single shard): NEW per-push/PR hard gate (0 surviving mutants, no continue-on-error). Fast enough to stay on the every-push path; preserves mutation coverage on the CLI surface. `test` is ungated so it runs on schedule too, satisfying both jobs' `needs: [test]`. Confirmed with actionlint (clean apart from the pre-existing custom self-hosted runner-label false positives) and a yaml.safe_load parse. Trace: skip Refs: #498 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Problem (#498)
The 16-shard rivet-core mutation matrix is non-gating (
continue-on-error) but runner-heavy: 16 shards × 45 min on the self-hostedlean-mempool. Running it on every push saturated the pool, queueing the actual gating jobs (test,clippy, the rivet-cli mutation gate) behind it for hours.Change
Split mutation testing into two jobs by cost/role:
mutants-corecron '0 3 * * *') +workflow_dispatchcontinue-on-error)mutants-cli(new)exit 1on surviving mutants)schedule:+workflow_dispatch:toon:.mutants-coregated withif: github.event_name == 'schedule' || github.event_name == 'workflow_dispatch'.mutants-cliis a new, fast, single-shard hard gate that keeps mutation coverage on the CLI surface on the every-push path.testis ungated, so it runs onscheduletoo — satisfying both jobs'needs: [test]. The heavy sweep still runs daily; it just no longer blocks interactive CI.Verification
actionlint .github/workflows/ci.yml— clean apart from the pre-existing custom self-hostedrunner-labelfalse positives (light,rust-cpu), which predate this change.python3 -c "import yaml; yaml.safe_load(...)"— parses.needs: [mutants](the old job name), so no dependents break.Closes #498.
🤖 Generated with Claude Code