[None][ci] waive pre-existing test failures on main - #18055
Conversation
|
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)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe integration waiver list now skips the LagunaXS NVFP4 test, six KV-cache scheduler tests, and the Eagle3 speculative test module. Each entry references an NVBug. ChangesIntegration test waivers
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: 🔵 Low · up to The change adds a targeted waiver for a pre-existing test failure. It is mergeable with explicit owner follow-up to confirm the affected test scope before QA review closes. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/bot run |
|
PR_Github #68183 [ run ] triggered by Bot. Commit: |
|
PR_Github #68183 [ run ] completed with state |
…sting failures on main; tracking bugs in the PR description) Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>
|
Closing: this waive doesn't hold up.
No tracking bug filed. If a genuine eagle3 flake shows up later it can be waived narrowly against a fresh open bug. |
Waives for pre-existing test failures on
main, each with a filed tracking bug. These failures block unrelated PRs; landing the waives here keeps them out of those PRs' diffs.unittest/_torch/speculative/test_eagle3.pyMaintained by pr-babysitter: entries are pruned automatically as
mainpicks their tests up, and the PR closes itself when nothing is left to carry. The branch is regenerated on each change — do not push to it.Dev Engineer Review
waives.txtformat and link each entry to an NVBug reference.QA Engineer Review
tests/integration/test_lists/waives.txt.