Skip to content

[None][chore] Increase GB200-4_GPUs-PyTorch shards - #14836

Merged
tburt-nv merged 1 commit into
NVIDIA:mainfrom
tburt-nv:user/tburt/gb200_shard
Jun 8, 2026
Merged

[None][chore] Increase GB200-4_GPUs-PyTorch shards#14836
tburt-nv merged 1 commit into
NVIDIA:mainfrom
tburt-nv:user/tburt/gb200_shard

Conversation

@tburt-nv

@tburt-nv tburt-nv commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

Description

GB200-4_GPUs-PyTorch gets timeouts too.

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-compatible or api-breaking. For api-breaking, include BREAKING in 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.

Summary by CodeRabbit

  • Tests
    • Enhanced test validation for SBSA SLURM scenarios with expanded test coverage.

Signed-off-by: Tyler Burt <195370667+tburt-nv@users.noreply.github.com>
@tburt-nv
tburt-nv requested a review from a team June 1, 2026 21:59
@tburt-nv
tburt-nv requested a review from a team as a code owner June 1, 2026 21:59
@tburt-nv

tburt-nv commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator Author

/bot run --stage-list "GB200-4_GPUs-PyTorch-1, GB200-4_GPUs-PyTorch-2, GB200-4_GPUs-PyTorch-3, GB200-4_GPUs-PyTorch-4"

@tburt-nv
tburt-nv enabled auto-merge (squash) June 1, 2026 21:59
@coderabbitai

coderabbitai Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 00b1a059-364f-422d-9929-7ef60777b9d8

📥 Commits

Reviewing files that changed from the base of the PR and between 059de9c and cebd654.

📒 Files selected for processing (1)
  • jenkins/L0_Test.groovy

📝 Walkthrough

Walkthrough

The pull request updates the Jenkins pipeline configuration to expand the SBSA SLURM test suite for GB200-4_GPUs-PyTorch from 2 to 4 parallel split groups by increasing the split-count parameter and adding stage mappings for the new split IDs 3 and 4.

Changes

Test Stage Configuration

Layer / File(s) Summary
GB200-4 PyTorch SBSA split configuration
jenkins/L0_Test.groovy
SBSA SLURM stage entries for GB200-4_GPUs-PyTorch-* update the split-count parameter from 2 to 4 for split IDs 1 and 2, and add new stage mappings for split IDs 3 and 4 to enable parallel execution across 4 test groups.

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description lacks critical detail: it only states 'GB200-4_GPUs-PyTorch gets timeouts too' without explaining the motivation, solution, test coverage, or addressing most checklist items. Expand description to explain why shards are increased (timeout mitigation), specify test coverage for the change, and ensure the PR checklist is properly reviewed.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: increasing shards for GB200-4_GPUs-PyTorch in Jenkins configuration.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #51427 [ run ] triggered by Bot. Commit: cebd654 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #51427 [ run ] completed with state SUCCESS. Commit: cebd654
/LLM/main/L0_MergeRequest_PR pipeline #40837 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

@mzweilz

mzweilz commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

/bot skip --comment "Tests already passed."

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #52631 [ skip ] triggered by Bot. Commit: cebd654 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #52631 [ skip ] completed with state SUCCESS. Commit: cebd654
Skipping testing for commit cebd654

Link to invocation

@tburt-nv
tburt-nv merged commit b8d17d7 into NVIDIA:main Jun 8, 2026
14 of 15 checks passed
2ez4bz pushed a commit to 2ez4bz/TensorRT-LLM that referenced this pull request Jun 8, 2026
Signed-off-by: Tyler Burt <195370667+tburt-nv@users.noreply.github.com>
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.

5 participants