[Fix] Mutation scope changes when main advances - #1655
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review. 📜 Recent review details⏰ Context from checks skipped due to timeout. (2)
🧰 Additional context used📓 Path-based instructions (3)Check strict typing and exhaustive behavior across normal, boundary, error, cancellation, retry, and compatibility paths.⚙️ CodeRabbit configuration file Files:
Require full commit SHA pins, least-privilege permissions, safe expression and shell interpolation, and trusted metadata handling.⚙️ CodeRabbit configuration file Files:
Act as an adversarial second-opinion reviewer.⚙️ CodeRabbit configuration file Files:
🔇 Additional comments (2)
📝 SummarySummary by CodeRabbit
WalkthroughThe mutation-testing workflow now derives ChangesMutation testing base selection
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The mutation scope now compares the merge result against its actual base snapshot, preventing unrelated main-branch changes from being included. No merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 7 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (7 passed)
Full details: Description checkExplanation The description explains what changed, why it changed, and the expected impact, but it omits the required Related GitHub Issue, Test Procedure, Pre-Submission Checklist, Documentation Updates, and Additional Notes sections.
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Review statusThis PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging. Current step: The required review sequence passed. Remaining merge requirements apply. Review-state labels are managed by this workflow; do not edit them manually. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
What changed
The mutation-diff workflow now compares a pull request's synthetic merge result with that merge commit's first parent, the exact
mainsnapshot GitHub used to create it. A regression test models a stale pull-request base followed by an unrelated executable change onmainand verifies only the pull-request file is selected.Why this change was made
PR #1505 changed from 499 to 624 reported executable lines after
mainadvanced even though its latest source commit added only 6 executable lines. The stale event base caused 119 executable lines from the already-merged coverage cache verifier to be charged to the PR.Impact
Mutation scope remains stable when
mainadvances and still uses merge-result line coordinates. The 500-line limit is unchanged: #1505's corrected scope is 505 executable lines, so it remains legitimately blocked by 5 lines rather than the erroneous 124-line overage.