Fix asynchronous clique table handoff - #1834
Conversation
Signed-off-by: Hugo Linsenmaier <hlinsenmaier@gmail.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe cut generator now retains a reference to the caller-owned clique-table pointer. A MIP regression test verifies asynchronous clique cuts on a triangle set-packing problem. ChangesClique-table lifecycle
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized concurrency fix ensures root separation sees the asynchronously completed clique table, restoring the intended clique and Zero-Half cut behavior without changing external interfaces or deployment requirements. No actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/ok to test 7ce3eb2 |
CI Test Summary✅ All 31 test job(s) passed. |
|
/merge |
The root-cut generator could retain a stale null snapshot of the clique table while that table was being constructed asynchronously.
Race sequence:
Three regressions bought stronger root bounds.
ns1208400incurred the largest cost without any root-gap improvement.