chore(node-suite): stop committing derived overall aggregate - #6698
Merged
Conversation
The baseline stored a top-level `overall` {pass,total,pct} block that no
code reads — the regression gate is 100% per-module (node_suite_regression_check.py
reads only `modules`). Every floor-bumping parity PR rewrote the same three
`overall` lines, so any two such PRs collided pairwise on that shared triple.
The stored value had also drifted stale (2820/2919 vs the real module sum
2834/2959), confirming it as write-only bookkeeping nobody maintained.
Remove the block and compute the overall from the per-module floors at report
time in node_suite_regression_check.py instead. Per-module data (the exhaustive
analysis) is untouched; the gate's pass/fail decision is unchanged.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe regression check now computes and prints an aggregate node suite baseline floor. The baseline JSON note no longer states that the overall summary equals the sum of per-module floors. ChangesNode suite baseline
Estimated code review effort: 1 (Trivial) | ~5 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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 was referenced Jul 26, 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.
Problem
test-parity/node_suite_baseline.jsonstored a top-leveloverall{pass,total,pct}block, but nothing reads it:scripts/node_suite_regression_check.pyreads only.get("modules", {})— the gate is 100% per-module.scripts/node_suite_run.pycomputes its own overall from the live run.overallkey.Because every floor-bumping parity PR rewrote those same three
overalllines, any two such PRs collided pairwise on that shared triple — currently blocking ~10 open parity PRs from rebasing cleanly.The stored value had also drifted stale (
2820/2919vs the real module sum2834/2959), confirming it as write-only bookkeeping nobody kept in sync.Change
overallblock from the baseline JSON (and drop the now-obsolete_schema.notesentence describing it).node_suite_regression_check.py, printed asbaseline floor overall: <sum>/<sum> (<pct>%).Per-module data — the exhaustive analysis — is untouched. The gate's pass/fail decision is unchanged (still per-module floors only). Each parity PR now edits only its own module block, so the conflict class is gone permanently.
Notes
Summary by CodeRabbit
New Features
Documentation