Repository navigation
[https://nvbugs/6966263][test] Re-waive the flaky CuTe DSL MoE NVFP4 act-fusion test at its moe/kernels path - #20800
Conversation
…act-fusion test at its moe/kernels path The directory waive from NVIDIA#20735 named the pre-move unittest/_torch/thop/parallel path and no longer matches; waive only the tracked test. Signed-off-by: Lori Ren <lorir@nvidia.com>
|
/bot run |
|
Automatically added "ci: full pre-merge approved" because this PR has satisfied the required GitHub review approvals. Unresolved review conversations and other required checks remain independent merge requirements. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe integration test waiver list adds a skip entry for a Blackwell Cute DSL MoE grouped-GEMM fusion test and removes the skip entry for ChangesIntegration test waiver updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to
|
|
PR_Github #79805 [ run ] triggered by Bot. Commit: |
|
PR_Github #79805 [ run ] completed with state |
…sl-moe-nvfp4 Signed-off-by: Lori Ren <lorir@nvidia.com> # Conflicts: # tests/integration/test_lists/waives.txt
|
/bot skip --comment "waiver conflict, unwaived cases have passed CI already" |
1 similar comment
|
/bot skip --comment "waiver conflict, unwaived cases have passed CI already" |
|
PR_Github #79998 [ skip ] triggered by Bot. Commit: |
|
PR_Github #79998 [ skip ] completed with state |
…ct-fusion relu2 test The kernel computes the activation and per-block amax in fp32, while the reference rounds the GEMM output and the Relu2 output to bf16 before fp4_quantize. Blocks whose scale factor sits near an E4M3 rounding midpoint then round to the adjacent code, which affects 2-5% of the blocks for Relu2, so the 95% exact-match threshold failed intermittently (~2.6% of runs for 8192-8-1-128-relu2). Lower it to 90%. Also remove the waiver of this test (nvbug 6966263, re-added at its moe/kernels path by NVIDIA#20800); nvbug 6971596 reports the same relu2 SF mismatch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: leslie-fang25 <leslief@nvidia.com>
Dev Engineer Review
The waiver now targets
test_cute_dsl_moe.py::test_nvfp4_gather_grouped_gemm_act_fusion_blackwellinstead of theunittest/_torch/thop/paralleldirectory. This limits the waiver to the flaky test and leaves other tests eligible to run. Review finding counts are unavailable.QA Engineer Review
Only
tests/integration/test_lists/waives.txtchanged. It removes the directory-level waiver and adds a waiver for the Blackwell Cute DSL MoE grouped-GEMM fusion test under NVBUG 6966263. The supplied CI report says the pipeline succeeded after automatic test retries. Coverage verdict: sufficient.Per-File QA Perspective
tests/integration/test_lists/waives.txt: The waiver targets the specific test at its moved path. Other tests are no longer excluded by this entry.Description
#20735 waived
unittest/_torch/thop/parallelunder nvbugs/6966263, but #20658 moved that directory's tests tounittest/_torch/moe/kernels/parallel, so the waive no longer matches anything and the flaky case runs again on main.This replaces it with a function-level waive of
test_cute_dsl_moe.py::test_nvfp4_gather_grouped_gemm_act_fusion_blackwell, the case the bug tracks. The old entry skipped the whole directory, includingtest_moe_densegemm.pyand the other CuTe DSL MoE tests; with the waive narrowed to this case, the rest of the directory runs again.Test Coverage
Waive change only; the waives.txt pre-commit checks (duplicates, entries exist in source) pass.
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.