[None][test] Split test_moe_backend TRTLLM by quant=None to avoid in-process IMA cascade - #16068
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 (3)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThis PR updates test list configuration files for B200 and B300 GPU test databases, splitting a single TRTLLM filter for the ChangesTest Selection Updates
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
Comment |
e80e813 to
5e40e0d
Compare
|
/bot run --disable-fail-fast |
|
PR_Github #58003 [ run ] triggered by Bot. Commit: |
|
PR_Github #58003 [ run ] completed with state |
|
/bot run --disable-fail-fast --extra-stage "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-1" |
|
PR_Github #58095 [ run ] triggered by Bot. Commit: |
|
PR_Github #58095 [ run ] completed with state
|
|
/bot help |
GitHub Bot Help
Provide a user friendly way for developers to interact with a Jenkins server. Run See details below for each supported subcommand. Details
Launch build/test pipelines. All previously running jobs will be killed.
kill
Kill all running builds associated with pull request. skip
Skip testing for latest commit on pull request. reuse-pipeline
Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break. |
|
/bot run --disable-reuse-test --disable-fail-fast --post-merge --stage-list “B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-2” |
1 similar comment
|
/bot run --disable-reuse-test --disable-fail-fast --post-merge --stage-list “B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-2” |
|
PR_Github #58159 [ run ] triggered by Bot. Commit: |
|
PR_Github #58159 [ run ] completed with state
|
|
/bot run --disable-reuse-test --disable-fail-fast --post-merge --stage-list “B300-PyTorch-Post-Merge-1, DGX_B200-PyTorch-Post-Merge-1, DGX_B200-PyTorch-Post-Merge-2” |
|
PR_Github #58180 Bot args parsing error: usage: /bot [-h] |
|
/bot run --disable-reuse-test --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-2" |
|
PR_Github #58184 [ run ] triggered by Bot. Commit: |
|
PR_Github #58184 [ run ] completed with state
|
|
/bot run --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-2" |
|
PR_Github #58229 [ run ] triggered by Bot. Commit: |
|
PR_Github #58229 [ run ] completed with state
|
|
/bot run --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-2" |
|
PR_Github #58325 [ run ] triggered by Bot. Commit: |
|
PR_Github #58325 [ run ] completed with state
|
|
/bot run --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-2" |
|
PR_Github #58347 [ run ] triggered by Bot. Commit: |
|
PR_Github #58347 [ run ] completed with state
|
|
/bot run --disable-reuse-test --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-*" |
|
/bot run --disable-reuse-test --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-*" |
…RTLLM MoE cases on Blackwell Signed-off-by: leslie-fang25 <leslief@nvidia.com>
…n Blackwell The blanket B300/DGX_B200 waives are superseded by the in-process cascade skips added in should_skip_trtllm (quant=None and e128 W4A16_MXFP4); the remaining TRTLLM MoE cases now run in CI. Signed-off-by: leslie-fang25 <leslief@nvidia.com>
917165b to
a554b2f
Compare
|
/bot run --disable-reuse-test --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-*" |
|
PR_Github #58964 [ run ] triggered by Bot. Commit: |
|
PR_Github #58964 [ run ] completed with state |
|
/bot run --disable-reuse-test --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-*" |
|
PR_Github #58975 [ run ] triggered by Bot. Commit: |
|
PR_Github #58975 [ run ] completed with state
|
|
/bot run --disable-fail-fast --post-merge --stage-list "B300-PyTorch-Post-Merge-1,DGX_B200-PyTorch-Post-Merge-*" |
|
PR_Github #59044 [ run ] triggered by Bot. Commit: |
|
PR_Github #59044 [ run ] completed with state |
a554b2f to
4b644c9
Compare
|
/bot run --disable-fail-fast |
|
The implementation has been modified based on offline discussion. @xxi-nv please kindly help to take a look again. |
|
PR_Github #59068 [ run ] triggered by Bot. Commit: |
|
/bot run --disable-fail-fast |
|
PR_Github #59112 [ run ] triggered by Bot. Commit: |
|
PR_Github #59068 [ run ] completed with state |
|
PR_Github #59112 [ run ] completed with state |
Split test_moe_backend TRTLLM by quant=None to avoid in-process IMA cascade
Summary by CodeRabbit
Description
Test Coverage
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.