[https://nvbugs/6272673][chore] Unwaive DeepSeek V3 Lite NVFP4 test#16398
Conversation
|
/bot run --disable-fail-fast |
Signed-off-by: Yuxian Qiu <142763828+yuxianq@users.noreply.github.com>
📝 WalkthroughWalkthroughUpdates integration-test SKIP waivers for ChangesDeepSeekV3Lite waiver updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
PR_Github #59336 [ run ] triggered by Bot. Commit: |
|
PR_Github #59336 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #59396 [ run ] triggered by Bot. Commit: |
|
PR_Github #59396 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #59457 [ run ] triggered by Bot. Commit: |
|
PR_Github #59457 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #59588 [ run ] triggered by Bot. Commit: |
|
PR_Github #59588 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #59849 [ run ] triggered by Bot. Commit: |
|
PR_Github #59849 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #59874 [ run ] triggered by Bot. Commit: |
|
PR_Github #59874 [ run ] completed with state |
Summary by CodeRabbit
Description
Remove the NVBug 6272673 waiver for the DeepSeek V3 Lite NVFP4 four-GPU test so the configuration runs in CI again.
The reported intermittent failure could not be reproduced in 100 consecutive executions on B300 x4.
Test Coverage
accuracy/test_llm_api_pytorch.py::TestDeepSeekV3Lite::test_nvfp4_4gpus[moe_backend=CUTLASS-mtp_nextn=0-tp4-fp8kv=True-attention_dp=True-cuda_graph=True-overlap_scheduler=True-low_precision_combine=False-torch_compile=True]PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.