fix(gates): gc-root-dominance defrag probe follows the file move (#7443) - #7543
Merged
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe GC root-dominance probe now detects the relocated old-generation source file, validates the defrag guard, and reports the selected path. Project version documentation and workspace metadata are updated to ChangesGC probe and release metadata
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
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.
_probe_old_defrag_off_by_defaultreadcrates/perry-runtime/src/gc/oldgen.rsto confirm old-page defrag is still opt-in. #7443 moved that code togc/oldgen_defrag.rs, so the probe stopped findingPERRY_GC_OLD_DEFRAGand began reporting "old-page defrag may now be unconditional" — on a tree where it is still gated exactly as before.This is worse than a red job. By the checker's own contract, this probe failing declares the reports it was suppressing to be real again — so a file rename silently converts a passing audit into a wall of false positives, in the gate family the entire #7341 rooting campaign depends on. Found by an agent working #7497, which flagged it alongside
gc-ratchetas red onmainfor reasons unrelated to its own PR.The probe now searches a candidate list and reports which source it validated, so the next split costs one line rather than a rotted premise; the failure message names the list.
Sabotage-verified both directions, because a repaired probe that can no longer fail is the worse outcome:
(True, 'gated on PERRY_GC_OLD_DEFRAG in .../oldgen_defrag.rs, empty selection when off')old_page_defrag_enabled()short-circuit deleted →(False, 'select_old_page_defrag_pages no longer short-circuits …')--self-testpasses.Summary by CodeRabbit