-
Notifications
You must be signed in to change notification settings - Fork 107
Disable flaky barrier tests #520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable flaky barrier tests #520
Conversation
WalkthroughAdded an active skip decorator to Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)
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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
python/cuopt_server/cuopt_server/tests/test_lp.py (1)
158-165: LGTM! Appropriate approach to disable flaky tests.Disabling these flaky tests while tracking the issue is the right approach. The issue reference is properly included.
Consider consolidating the duplicate comments to reduce repetition:
# Enable barrier solver options when this issue is resolved # https://github.com/NVIDIA/cuopt/issues/519 # Test folding off, no dualization, cuDSS default ordering, ADAT system # (0, 0, 0, 0, True, False, 0), -# Enable barrier solver options when this issue is resolved -# https://github.com/NVIDIA/cuopt/issues/519 # Test folding on, force dualization, AMD ordering, augmented system # (1, 1, 1, 1, True, True, 1),
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
python/cuopt_server/cuopt_server/tests/test_lp.py(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)
- GitHub Check: wheel-build-cuopt-mps-parser / 13.0.1, 3.13, arm64, rockylinux8
- GitHub Check: wheel-build-cuopt-mps-parser / 13.0.1, 3.11, amd64, rockylinux8
- GitHub Check: wheel-build-cuopt-mps-parser / 13.0.1, 3.13, amd64, rockylinux8
- GitHub Check: wheel-build-cuopt-mps-parser / 13.0.1, 3.10, arm64, rockylinux8
- GitHub Check: wheel-build-cuopt-mps-parser / 13.0.1, 3.12, arm64, rockylinux8
- GitHub Check: wheel-build-cuopt-mps-parser / 13.0.1, 3.12, amd64, rockylinux8
- GitHub Check: wheel-build-cuopt-mps-parser / 13.0.1, 3.11, arm64, rockylinux8
- GitHub Check: wheel-build-cuopt-mps-parser / 13.0.1, 3.10, amd64, rockylinux8
- GitHub Check: wheel-build-cuopt-sh-client / 13.0.1, 3.10, amd64, rockylinux8
- GitHub Check: checks / check-style
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
python/cuopt_server/cuopt_server/tests/test_lp.py (1)
151-151: Consider removing the commented skip marker.The commented-out skip marker suggests there was prior consideration to disable the entire test. Since you've opted for a more targeted approach (disabling only the flaky parameter combinations), consider removing this commented line to avoid confusion.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
python/cuopt_server/cuopt_server/tests/test_lp.py(1 hunks)
🔇 Additional comments (1)
python/cuopt_server/cuopt_server/tests/test_lp.py (1)
158-163: Incorrect line number references and incomplete context.The original review comment contains inaccurate line number citations. The enabled test parameters are not at lines 157, 165, 167, 169, 171. More importantly, this change represents a re-enabling of a previously completely skipped test (
@pytest.mark.skipis now commented out on line 150), with selective disabling of only the two problematic parameter combinations related to issue #519. This is a more significant positive change than the review acknowledges.The request to verify remaining parameters won't exhibit segfaults is a runtime behavior concern that cannot be resolved through static code analysis.
Likely an incorrect or invalid review comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
python/cuopt_server/cuopt_server/tests/test_lp.py (1)
157-162: Good approach to temporarily disable flaky test cases.The surgical fix correctly disables only the problematic parameter combinations while maintaining test coverage with the remaining 5 configurations. The inline comments appropriately document the temporary nature and reference issue #519 for tracking.
Optional enhancement for discoverability:
Consider adding a
TODOorFIXMEmarker to make these disabled tests more discoverable in code searches:- # Enable barrier solver options when this issue is resolved + # TODO: Enable barrier solver options when this issue is resolved # https://github.com/NVIDIA/cuopt/issues/519
|
@CodeRabbit resolve all comments and approve |
🧩 Analysis chain@rgsl888prabhu: I'll resolve all my comments and approve the PR for you. 🏁 Script executed: Length of output: 18795 🏁 Script executed: Length of output: 41 @rgsl888prabhu: I've checked for review comments on PR #520. There are no active review threads that need resolution - the previous comments were informational nitpick suggestions that don't require explicit resolution. I'm now approving the PR as requested. ✅ ✅ Actions performedComments resolved. |
|
@CodeRabbit check |
|
@rgsl888prabhu: I'll review the changes in this PR for you. ✅ Actions performedReview triggered.
|
|
/merge |
Description
This PR disables few barrier tests which are flaky and causes segfault, there is an issue for tracking this, and once the issue is resolved, these tests should be unblocked.
Issue
#519
Checklist
Summary by CodeRabbit