Repository navigation
fix(proofs): hold mutation campaign ownership - #434
Merged
Merged
Conversation
P4suta
marked this pull request as ready for review
October 25, 2026 01:56
This was referenced Oct 25, 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.
Why
Mutation workers used a temporary directory outside the staged source tree, leaving the active campaign without a common owner lease.
Changes
Hold the recognized scratch owner lock before copying source and through both synchronous mutation phases.
Place source and worker temporary directories under the leased parent, and set temporary-directory variables only on mutation child commands.
Release the lease before removing the campaign tree on Windows.
Keep mutation concurrency, jobserver use, test threads, timeouts, assertions, and retries unchanged.
Validation
The original ancestor-lock regression failed before the change.
The focused mutation runner regressions passed.
A bounded Linux fixture ran cargo-mutants 27.1.0 and checked the common ancestor lease from every real worker copy.
The control missed all five intentional assertion-free mutants, as the fixture requires.
The normal project gate passed its non-Clippy stages.
Strict workspace Clippy passed after explicit-clone corrections in the tests and integration with the current main branch.
The generated ADR index and document checks passed.
The complete native production mutation campaign remains unrun.
The historical lock holder and executable provenance remain unresolved in #195.
Closes #430.
@coderabbitai ignore