test(codegen): isolate the default feedback lane - #9999
proggeramlug wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe closure-specialization test now isolates profiling environment variables before asserting the default typed feedback behavior. A changelog entry documents the fix. ChangesTyped feedback test isolation
Priority: ⚪ Not assessed Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The closure-specialization test now reliably exercises the default feedback behavior even when profiling environment settings are inherited or changed by parallel tests. No production behavior changes, and the change is ready to merge. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
(cherry picked from commit 14863a9)
|
Landed via #10001 (rebase train; author commits retained). Audited head: |
Test-only fix
The closure-specialization test asserts that pure feedback recording calls are absent, but did not acquire the suite's environment lock or disable the profiling settings. Other tests in this same parallel suite temporarily enable those settings, causing scoped CI on unrelated codegen PRs to fail at typed_feedback.rs:1171.
Join the existing poison-tolerant lock and scoped environment guards. No production compiler/runtime behavior changes. Based directly on main; independent of the compatibility changes.
Validation
Baseline CI issues, independently confirmed in main run 34232917409: stale public benchmark evidence and native_stack::tests::stack_top_respects_custom_thread_stack_sizes. This PR does not alter or suppress either gate.
Summary by CodeRabbit
Bug Fixes
Documentation