🐛 fix(ci): make mutation failures decisive - #1713
Merged
Merged
Conversation
Stop mutation runs after the first behavioral failure so one mutant cannot consume a shard while unrelated tests continue. Exercise the driver state transitions and plugin registration contracts that the nightly shard left unobserved. Separate shared auth from extension settings so plugins without extension fields have no empty contract to mutate. Keep metrics overflow from interrupting scheduler completion.
Merging this PR will not alter performance
Comparing 
Footnotes
|
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.
Nightly mutation shards were exhausting their CI budget after already finding a behavioral failure. One shard produced 363 outcomes from 543 candidates before its 180-minute limit, leaving 180 unrecorded, while driver shard 4 timed out after a mutated metrics counter interrupted scheduler completion. 🧬
just mutationnow selects a fail-fast nextest profile, which lets cargo-mutants record the first caught mutation without continuing through unrelated cases. Public driver interfaces make cache refresh, retry policy, operation timestamps, retention, and index descriptions observable. Auth registrations identify whether an ecosystem uses only shared auth or adds extension fields. OCI therefore no longer implements empty field/default hooks, while PyPI supplies its extension schema in registration data. Job-start counters saturate so monitoring overflow cannot interrupt scheduler completion.Cargo-mutants discovers candidates by parsing the source AST before builds and does not evaluate
cfgpredicates. This change does not exclude the resulting wasm-onlyhydrateartifact; cfg-aware discovery remains tracked in upstream issue #50 and design PR #623, while non-Cargo verifier support remains upstream issue #638.