[None][chore] increase test shards

[tburt-nv]

Description

More shards, fewer timeouts

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

• Chores
  • Updated test execution configuration parameters to optimize parallel test processing and resource allocation across supported hardware platforms for improved testing efficiency.

[tburt-nv]

/bot run --stage-list "DGX_H100-PyTorch-1, DGX_H100-PyTorch-2, DGX_H100-PyTorch-3, DGX_H100-PyTorch-4, DGX_H100-PyTorch-5, DGX_H100-PyTorch-6, B300-PyTorch-1, B300-PyTorch-2, B300-PyTorch-3"

[coderabbitai]

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: 75661ace-c11c-43e5-92ab-1427cc835e8d

📥 Commits

Reviewing files that changed from the base of the PR and between 74d7c3a and 746f1bc.

📒 Files selected for processing (1)

• jenkins/L0_Test.groovy

---

📝 Walkthrough

Walkthrough

This PR updates SLURM test configuration mappings in Jenkins to expand test parallelization. DGX_H100-PyTorch parallel groups increase from 4 to 6, and B300-PyTorch expands from a single group to three groups, each with adjusted split-count parameters.

Changes

Test Parallelization Configuration Updates

Layer / File(s)	Summary
Test parallelization group expansion jenkins/L0_Test.groovy	DGX_H100-PyTorch configuration splits from 4 to 6 groups with updated split-count, and B300-PyTorch expands from 1 to 3 split groups with corresponding parameter adjustments in the x86SlurmTestConfigs map.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes the required title format with ticket type, but the Description and Test Coverage sections lack detail explaining the rationale and test safeguards.	Expand the Description section to explain why increasing shards reduces timeouts, and clarify what tests validate these configuration changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: increasing test shards to improve test parallelization and reduce timeouts.
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]

PR_Github #51099 [ run ] triggered by Bot. Commit: 746f1bc Link to invocation

[tensorrt-cicd]

PR_Github #51099 [ run ] completed with state SUCCESS. Commit: 746f1bc
/LLM/main/L0_MergeRequest_PR pipeline #40537 (Partly Tested) completed with status: 'SUCCESS'
Pipeline passed with automatic retried tests. Check the rerun report for details.

CI Report

Link to invocation