Repository navigation
ci: nightly workspace mutants, drop the PR shards - #739
Merged
Merged
Conversation
Package-scoped PR shards treated a higher journey as a miss. The night spends 90 minutes on new lines first, then a cursor through older mutants, and a missed mutant is an artifact. Co-authored-by: Cursor <cursoragent@cursor.com>
Hero-Gamer
added a commit
to Hero-Gamer/rbitcoin
that referenced
this pull request
Sep 24, 2026
- Only the 'new survivors vs baseline' path → exit 0 - Actual error conditions (missing files/data) still fail as before - ::error:: → ::notice::; clearly states non-blocking - Aligns with nightly mutants model, no PR gating
This was referenced Sep 24, 2026
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
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.
Summary
mutants (1/4)–(4/4). A same-crate test is not required to satisfy cargo-mutants.mutants.ymlruns every night at 07:00 UTC (workflow_dispatchtoo). Budget is 90 minutes,-j 1,--test-workspace=true, so a journey outside the mutated crate can catch the mutant. New diff lines since the cursor go first; whatever time is left walks a rotating backlog. A 20 minute mutant timeout is a hang, and the cursor moves past it.MISSEDis uploaded (mutants-nightly) and printed in the job summary. It does not fail the workflow and it does not block merge. The cursor artifact ismutants-cursor.90 minutes rather than 60: one workspace suite is several minutes, and two in parallel do not fit the runner. An hour finishes a couple of mutants after setup. Ninety can clear a normal day's new mutants and still move the backlog.
Operator step before merge
Ruleset Protected (
20615233) still requiresmutants (1/4)throughmutants (4/4). This token cannot edit rulesets. Remove those four contexts or every pull request, including this one, waits for checks that will never start. Leaveqc,test,windows,macos,coverage, andrelease-extra.Test plan
./scripts/mutants-queue.test.sh./scripts/pr-checks-watch.test.shMade with Cursor