test(flow): cover wildcard conflict rule and HasScheduleConflict - #5073
test(flow): cover wildcard conflict rule and HasScheduleConflict#5073kdhulipala-wq wants to merge 2 commits into
Conversation
Signed-off-by: Krishna Dhulipala <kdhulipala@nvidia.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 (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan includes up to 12 reviews per rolling hour; 11 remain after this review. Summary by CodeRabbit
WalkthroughThe change adds a test helper and expands conflict-resolution coverage. Tests verify wildcard decommission matching and ChangesConflict resolution tests
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change adds coverage for wildcard conflict handling and schedule-conflict detection without changing production behavior; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
🔐 TruffleHog Secret Scan✅ No secrets or credentials found! Your code has been scanned for 700+ types of secrets and credentials. All clear! 🎉 🕐 Last updated: 2026-08-17 20:25:33 UTC | Commit: 3289201 |
Signed-off-by: Krishna Dhulipala <kdhulipala@nvidia.com>
**This is a re-issue of an older pull request 4684 to restart the CI pipeline which was broken on the older version of main.
Two test gaps from the rack decommission follow-up review (Kun's notes on #4408).
TestBuiltinRule: adds two cases for the decommission wildcard:
TestResolver_HasScheduleConflict: new test for the coarse-grained schedule-conflict check, which was previously untested. Cases cover:
bring_upanddecommissionwildcard matches (both directions)decommissionblocking an unlisted operation type via wildcard Binject_expectationnot conflicting with power or firmware