Skip to content

[https://nvbugs/6517844][test] Unwaive DeepSeek V3 Lite RTX Pro 6000D test - #17364

Open
nv-lschneider wants to merge 1 commit into
NVIDIA:mainfrom
nv-lschneider:waive-deepseek-v3-lite-rtxpro6000d
Open

[https://nvbugs/6517844][test] Unwaive DeepSeek V3 Lite RTX Pro 6000D test#17364
nv-lschneider wants to merge 1 commit into
NVIDIA:mainfrom
nv-lschneider:waive-deepseek-v3-lite-rtxpro6000d

Conversation

@nv-lschneider

@nv-lschneider nv-lschneider commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

FIx merged with #16956
This just unwaives the test.

Dev Engineer Review

  • Removed the waiver for TestDeepSeekV3Lite::test_bfloat16_4gpus with ep4, mtp_nextn=2, and torch_compile=False.
  • The change is limited to tests/integration/test_lists/waives.txt.
  • The waiver removal is consistent with the objective to re-enable the test for RTX Pro 6000D GPUs.
  • No code, API, performance, or error-handling changes were made.

QA Engineer Review

  • Modified tests/integration/test_lists/waives.txt.
  • Removed the waiver entry for TestDeepSeekV3Lite::test_bfloat16_4gpus.
  • No test code changed.
  • CBTS coverage data is unavailable. Verdict: needs follow-up.
  • Run the requested RTXPro6000D-4_GPUs-PyTorch-Post-Merge-* bot test stages.
  • Please check this after reviewing the above items as appropriate for this PR.

@nv-lschneider

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "RTXPro6000D-4_GPUs-PyTorch-Post-Merge-*"

Signed-off-by: Ludwig Schneider <lschneider@nvidia.com>
@nv-lschneider
nv-lschneider force-pushed the waive-deepseek-v3-lite-rtxpro6000d branch from cdcd367 to 7f642ef Compare August 6, 2026 12:41
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

Removed the waiver for TestDeepSeekV3Lite::test_bfloat16_4gpus with ep4, mtp_nextn=2, and torch_compile=False.

Changes

Cohort / File(s) Summary
Test waiver cleanup
tests/integration/test_lists/waives.txt
Removes the waiver associated with NVBugs issue 6517844.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: brnguyen2, stanleysun639, tburt-nv

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description states the change but omits the required Description and Test Coverage sections and provides no specific test details. Add the required Description and Test Coverage sections, and identify the relevant RTX Pro 6000D test stages or validation results.
✅ Passed checks (4 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly identifies the NVBugs issue and the primary change: unwaiving the DeepSeek V3 Lite RTX Pro 6000D test.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64343 [ run ] triggered by Bot. Commit: 7f642ef Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64343 [ run ] completed with state FAILURE. Commit: 7f642ef
/LLM/main/L0_MergeRequest_PR pipeline #52239 (Partly Tested) completed with status: 'UNSTABLE'

CI Report

⚠️ Multi-GPU Label Required:
Multi-GPU tests require the ci: full pre-merge approved label on this PR. Ask a member of NVIDIA/trt-llm-ci-approvers to add the label, then re-trigger CI with the same bot command (no rebase needed).

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

@nv-lschneider

Copy link
Copy Markdown
Collaborator Author

/bot run --extra-stage "RTXPro6000D-4_GPUs-PyTorch-Post-Merge-*"

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64356 [ run ] triggered by Bot. Commit: 7f642ef Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64356 [ run ] completed with state SUCCESS. Commit: 7f642ef
/LLM/main/L0_MergeRequest_PR pipeline #52250 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@brnguyen2 brnguyen2 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving — the comments below are optional touch-ups, not blockers.

Matches the bug — the fix in #16956 landed and the bug asks for exactly this unwaive.

Two CI notes before merging:

  • The test only runs post-merge, so a plain /bot run won't cover it. Run /bot run --extra-stage "RTXPro6000D-4_GPUs-PyTorch-Post-Merge-1, RTXPro6000D-4_GPUs-PyTorch-Post-Merge-2" — it failed in both stages, not just -2.
  • The removed line has no GPU prefix, so it was skipping this parametrization on B200/B300/GB300 too (l0_dgx_b200.yml, l0_dgx_b300.yml, l0_gb300_multi_gpus.yml). Worth adding those multi-GPU post-merge stages as well so the re-enable doesn't turn into a post-merge surprise on a platform nobody checked.

@nv-lschneider

Copy link
Copy Markdown
Collaborator Author

/bot run --extra-stage "RTXPro6000D-4_GPUs-PyTorch-Post-Merge-1,RTXPro6000D-4_GPUs-PyTorch-Post-Merge-2,DGX_B300-4_GPUs-PyTorch-Post-Merge-1,DGX_B300-4_GPUs-PyTorch-Post-Merge-2,GB300-4_GPUs-PyTorch-Post-Merge-1,GB300-4_GPUs-PyTorch-Post-Merge-2,GB300-4_GPUs-PyTorch-Post-Merge-3"

@nv-lschneider

Copy link
Copy Markdown
Collaborator Author

Thanks for the review, I am broadening the CI coverage to get full coverage.
Thanks for the detailed reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants