[None][chore] Add test lists with multi-gpu test to CI multi-gpu test trigger files

[pengbowang-nv]

Summary by CodeRabbit

• Chores
  • Updated test detection logic to recognize additional test configurations and newly supported GPU types, ensuring more comprehensive testing coverage in multi-GPU environments.

Description

Add test lists with multi-gpu tests to CI multi-gpu test trigger files, so that we can avoid PR for adding a test to multi-gpu test list get merged without triggering and runing multi-gpu tests.

Note: tests/integration/test_lists/test-db/l0_gb300.yml and tests/integration/test_lists/test-db/l0_rtx_pro_6000.yml contains both single gpu and multi gpu tests. Adding them to avoid missing.

file	system_gpu_count
tests/integration/test_lists/test-db/l0_gb300.yml	gte:1/lte:4
tests/integration/test_lists/test-db/l0_rtx_pro_6000.yml	gte:1/lte:1, gte:4/lte:4

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)

• 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.

[pengbowang-nv]

/bot help

[github-actions]

GitHub Bot Help

/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...

Provide a user friendly way for developers to interact with a Jenkins server.

Run /bot [-h|--help] to print this help message.

See details below for each supported subcommand.

Details

run [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental) --high-priority]

Launch build/test pipelines. All previously running jobs will be killed.

--reuse-test (optional)pipeline-id (OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.

--disable-reuse-test (OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.

--disable-fail-fast (OPTIONAL) : Disable fail fast on build/tests/infra failures.

--skip-test (OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.

--stage-list "A10-PyTorch-1, xxx" (OPTIONAL) : Only run the specified test stages. Supports wildcard * for pattern matching (e.g., "*PerfSanity*" matches all stages containing PerfSanity). Examples: "A10-PyTorch-1, xxx", "PerfSanity". Note: Does NOT update GitHub check status.

--gpu-type "A30, H100_PCIe" (OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.

--test-backend "pytorch, cpp" (OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline status.

--only-multi-gpu-test (OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.

--disable-multi-gpu-test (OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.

--add-multi-gpu-test (OPTIONAL) : Force run the multi-GPU tests in addition to running L0 pre-merge pipeline.

--post-merge (OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.

--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Supports wildcard * for pattern matching. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx", --extra-stage "Post-Merge".

--detailed-log (OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.

--debug (OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in the stage-list parameter to access the appropriate container environment. Note: Does NOT update GitHub check status.

--high-priority (OPTIONAL) : Run the pipeline with high priority. This option is restricted to authorized users only and will route the job to a high-priority queue.

kill

kill

Kill all running builds associated with pull request.

skip

skip --comment COMMENT

Skip testing for latest commit on pull request. --comment "Reason for skipping build/test" is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

reuse-pipeline

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR updates Jenkins pipeline logic to recognize additional GPU and multi-node test configurations as triggers for multi-GPU test runs. The getMultiGpuFileChanged() function's relatedFileList is expanded with new test-db YAML patterns for B200, GB200, GB300, and DGX H200 variants, replacing a specific hardcoded entry with more comprehensive pattern matching.

Changes

Multi-GPU File Change Detection

Layer / File(s)	Summary
Multi-GPU file change detection patterns jenkins/L0_MergeRequest.groovy	The getMultiGpuFileChanged function's relatedFileList is expanded with 31 additional lines covering multi-GPU and multi-node test-db YAML patterns across B200/GB200/GB300/DGX H200 and VERL variants, replacing the previous hardcoded l0_dgx_h200.yml entry with more flexible pattern-based detection.

Possibly related PRs

• NVIDIA/TensorRT-LLM#13594: Enables/disables the exact GB300 multi-nodes perf-sanity test-db YAMLs that this PR now treats as multi-GPU relevant in the change-detection logic.

Suggested reviewers

• niukuo
• ZhanruiSunCh
• dpitman-nvda

---

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title accurately describes the main change: adding test lists with multi-GPU tests to CI multi-GPU test trigger files, which matches the changeset content.
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.
Description check	✅ Passed	The PR description includes a clear explanation of the purpose (adding test lists to CI multi-GPU test triggers) and provides a helpful table showing affected files and their GPU configurations.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

[pengbowang-nv]

/bot run --skip-test

[tensorrt-cicd]

PR_Github #48152 [ run ] triggered by Bot. Commit: d594f05 Link to invocation

[tensorrt-cicd]

PR_Github #48152 [ run ] completed with state SUCCESS. Commit: d594f05
/LLM/main/L0_MergeRequest_PR pipeline #37974 (Partly Tested) completed with status: 'SUCCESS'

CI Report

Link to invocation

[pengbowang-nv]

/bot run

[tensorrt-cicd]

PR_Github #48350 [ run ] triggered by Bot. Commit: e27185f Link to invocation

[tensorrt-cicd]

PR_Github #48350 [ run ] completed with state SUCCESS. Commit: e27185f
/LLM/main/L0_MergeRequest_PR pipeline #38156 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

[pengbowang-nv]

/bot run --disable-fail-fast

[tensorrt-cicd]

PR_Github #50525 [ run ] triggered by Bot. Commit: a03fbde Link to invocation

[tensorrt-cicd]

PR_Github #50525 [ run ] completed with state SUCCESS. Commit: a03fbde
/LLM/main/L0_MergeRequest_PR pipeline #40032 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

[pengbowang-nv]

/bot run

[tensorrt-cicd]

PR_Github #50667 [ run ] triggered by Bot. Commit: a03fbde Link to invocation

[tensorrt-cicd]

PR_Github #50667 [ run ] completed with state SUCCESS. Commit: a03fbde
/LLM/main/L0_MergeRequest_PR pipeline #40157 completed with status: 'SUCCESS'

CI Report

Link to invocation