Repository navigation
test: assert the import-lock precondition instead of assuming it - #429
Conversation
The contention check blocked a release: it held the lock on a second connection, then required commit() to refuse — but never verified that the second connection had actually acquired the lock. When it had not, commit() legitimately succeeded and the check failed for a reason unrelated to what it tests, intermittently and without saying anything useful. The precondition is now asserted (with a couple of retries), and both messages carry what they observed: the outcome, the measured wait, the lock name and who holds it. A failure now either names a real defect or explains itself.
|
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 (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughIl test dell’import CSV conteso ora verifica l’acquisizione effettiva del lock MySQL prima del ChangesTest dell’import CSV conteso
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to The PR improves lock-contention test reliability and diagnostics without introducing an identified merge-blocking risk. 🚥 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 |
Test-only fix for the flaky import-lock contention check that blocked the 0.7.84 release preflight: the precondition (the blocking connection actually holding the lock) is now asserted instead of assumed, and both messages carry the observed evidence.
Summary by CodeRabbit