Skip to content

Conversation

@chzblych
Copy link
Collaborator

@chzblych chzblych commented Jan 17, 2026

Summary by CodeRabbit

  • Documentation
    • Updated installation documentation with CUDA 13.1 and PyTorch 2.9.1 requirements
    • Updated support matrix with latest versions of dependencies
    • Added compatibility notes regarding PyTorch wheel compatibility with container environments and recommendations for pre-built wheels

✏️ Tip: You can customize this high-level summary in your review settings.

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)

  • 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

/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)]

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. Examples: "A10-PyTorch-1, xxx". 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. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".

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

For guidance on mapping tests to stage names, see docs/source/reference/ci-overview.md
and the scripts/test_to_stage_mapping.py helper.

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.

Signed-off-by: qqiao <qqiao@nvidia.com>
Signed-off-by: Yanchao Lu <yanchaol@nvidia.com>
Co-authored-by: Yanchao Lu <yanchaol@nvidia.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 17, 2026

📝 Walkthrough

Walkthrough

This PR updates version references across documentation and CI configuration files. CUDA is updated from 13.0 to 13.1, PyTorch from 2.9.0 to 2.9.1, and Triton repository tags from r25.10 to r25.12. Support matrix references are updated to align with newer container and TensorRT versions, and a sanity check configuration is removed.

Changes

Cohort / File(s) Summary
Documentation Version Updates
README.md, docs/source/installation/linux.md, docs/source/legacy/reference/support-matrix.md
Updated CUDA (13.0→13.1), PyTorch (2.9.0→2.9.1), and container/TensorRT version references (25.10→25.12, 10.13→10.14). Added compatibility notes regarding PyTorch 2.9.1 wheel usage with NVIDIA containers.
CI Build Configuration
jenkins/Build.groovy
Updated Triton repository tags from r25.10 to r25.12 for cmake invocations.
CI Test Configuration
jenkins/L0_Test.groovy
Updated NVIDIA_TRITON_SERVER_VERSION from 25.10 to 25.12 in test list check; removed PY312-UB2404 block from aarch64 sanity check configurations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description is completely empty. Only the template and GitHub bot help section are present with no actual description of changes, rationale, or test coverage. Add a clear description explaining: (1) what versions are being updated (CUDA 13.1, PyTorch 2.9.1, Triton 25.12), (2) why these updates are necessary, and (3) which tests validate these documentation and build configuration changes.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: updating upgrade-related documentation and dependencies for release 1.2 across README, installation docs, support matrix, and build scripts.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/source/installation/linux.md`:
- Around line 19-20: Rewrite the sentence that precedes the pip command to fix
grammar and clarify compatibility: replace the fragment "By default, PyTorch
CUDA 12.8 package is installed. Since PyTorch CUDA 13.0 package to align with
the CUDA version used for building TensorRT LLM wheels." with a single clear
sentence explaining that we specify the cu130 wheel to match the CUDA family
used to build TensorRT-LLM and that the cu130 (CUDA 13.0) wheel is
forward-compatible with a CUDA 13.1 system; ensure the pip invocation shown
(pip3 install torch==2.9.1 torchvision --index-url
https://download.pytorch.org/whl/cu130) remains unchanged.
🧹 Nitpick comments (1)
jenkins/L0_Test.groovy (1)

3434-3445: Add a tracking reference for the PyTorch compatibility workaround.

Lines 3434-3445 document a PyTorch incompatibility workaround; consider linking a tracking issue/bug ID so it’s clear when to revert the temporary configuration.

Signed-off-by: Yanchao Lu <yanchaol@nvidia.com>
@chzblych chzblych merged commit 0096b50 into main Jan 17, 2026
7 checks passed
@chzblych chzblych deleted the cherry-pick/release-docs branch January 17, 2026 16:14
greg-kwasniewski1 pushed a commit to nv-auto-deploy/TensorRT-LLM that referenced this pull request Jan 18, 2026
…) (NVIDIA#10773)

Signed-off-by: qqiao <qqiao@nvidia.com>
Signed-off-by: Yanchao Lu <yanchaol@nvidia.com>
Co-authored-by: Emma Qiao <qqiao@nvidia.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.

2 participants