[TRTLLM-10820][infra] Update dependencies to algin with NGC PyTorch 26.02 stack#11227
[TRTLLM-10820][infra] Update dependencies to algin with NGC PyTorch 26.02 stack#11227EmmaQiaoCh wants to merge 54 commits intoNVIDIA:mainfrom
Conversation
|
/bot run --stage-list "Build-Docker-Images" |
|
PR_Github #34614 [ run ] triggered by Bot. Commit: |
📝 WalkthroughWalkthroughThis pull request updates CUDA from 13.1.0 to 13.1.1 and bumps the base container image from 25.12 to 26.01 across documentation, Docker configurations, CI/CD pipelines, and dependency specifications. Related NVIDIA libraries are also version-bumped to maintain compatibility. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docker/common/install_tensorrt.sh`:
- Around line 6-8: Update the stale comment that references rel-25-12 to
rel-26-01 so it matches the updated DLFW version and other files; edit the
comment above CUDA_VER="13.1" (the line mentioning the NVIDIA docs link) to
point to
https://docs.nvidia.com/deeplearning/frameworks/pytorch-release-notes/rel-26-01
and ensure the comment wording aligns with related references in
requirements.txt.
|
PR_Github #34614 [ run ] completed with state
|
|
/bot run |
|
/bot run --stage-list "Build-Docker-Images" |
|
PR_Github #34874 [ run ] triggered by Bot. Commit: |
|
/bot run --disable-fail-fast |
|
PR_Github #34983 [ run ] triggered by Bot. Commit: |
|
PR_Github #34983 [ run ] completed with state
|
|
/bot run --disable-fail-fast |
|
PR_Github #35299 [ run ] triggered by Bot. Commit: |
|
PR_Github #35299 [ run ] completed with state
|
|
I've opended bug(https://nvbugspro.nvidia.com/bug/5884997) for the failures in latest ci, and will waive them first. |
|
/bot run --stage-list "Build-Docker-Images" --comment "Rebuild image due to update for triton image" |
|
PR_Github #35472 Bot args parsing error: usage: /bot [-h] |
|
/bot run --stage-list "Build-Docker-Images" |
|
PR_Github #35476 [ run ] triggered by Bot. Commit: |
|
PR_Github #35476 [ run ] completed with state |
|
/bot run --disable-fail-fast |
|
PR_Github #35608 [ run ] triggered by Bot. Commit: |
EmmaQiaoCh
requested review from
QiJune,
SimengLiu-nv,
dongjiyingdjy,
hypdeb,
liji-nv and
omera-nv
EmmaQiaoCh
force-pushed
the
emma/upgrade_dlfw_2601
branch
from
fef5bea to
57aabe8
Compare
Signed-off-by: Emma Qiao <qqiao@nvidia.com>
|
Please note that I moved the changes to anothe PR(#12102) and will close this one. |
|
PR_Github #38535 [ run ] completed with state
|
5 participants
Summary by CodeRabbit
Chores
Documentation
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 thestage-listparameter 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.mdand the
scripts/test_to_stage_mapping.pyhelper.kill
killKill all running builds associated with pull request.
skip
skip --comment COMMENTSkip 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-pipelineReuse 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.