Skip to content

Conversation

ZhanruiSunCh
Copy link
Collaborator

@ZhanruiSunCh ZhanruiSunCh commented Oct 8, 2025

Summary by CodeRabbit

  • Bug Fixes

    • Ensured CUDA 13 compatibility on x86_64 by switching dependency to pytorch-triton 3.3.1 (replacing public triton).
  • Chores

    • Simplified Docker image build by removing post-install Triton adjustments, reducing build complexity and side effects.
  • Tests

    • Removed CUDA 13-specific Triton workaround from CI tests for Python 3.12 (DLFW), aligning tests with the new dependency setup.

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

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

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.

@ZhanruiSunCh ZhanruiSunCh requested review from a team as code owners October 8, 2025 05:57
@ZhanruiSunCh ZhanruiSunCh force-pushed the user/zhanruis/1008_remove_triton_war_code branch from 51fed7d to 83d93f7 Compare October 8, 2025 05:57
@ZhanruiSunCh
Copy link
Collaborator Author

/bot run --stage-list "Build-Docker-Images"

Copy link
Contributor

coderabbitai bot commented Oct 8, 2025

📝 Walkthrough

Walkthrough

Removed Triton post-install/metadata manipulation from Dockerfile and Jenkins CI script. Switched dependency from triton to pytorch-triton for x86_64 in requirements. Overall, eliminates custom renaming/RECORD edits and CUDA 13 workaround, standardizing on pytorch-triton installation.

Changes

Cohort / File(s) Summary
Docker image build cleanup
docker/Dockerfile.multi
Deleted non-Red Hat conditional post-install block that rewrote Triton packaging (renaming pytorch_triton→triton, METADATA/RECORD edits, ldconfig/logging).
CI test pipeline simplification
jenkins/L0_Test.groovy
Removed CUDA 13 workaround for PY312-DLFW path that installed nightly Triton and rewrote package metadata/files.
Dependency switch for x86_64
requirements.txt
Commented out triton==3.3.1; platform_machine == "x86_64" and added pytorch-triton==3.3.1; platform_machine == "x86_64" with note about CUDA 13 support.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The pull request description consists only of the unmodified repository template and contains no actual title, description of changes, test coverage details, or checklist updates, so it does not follow the required structure or provide any context for reviewers to understand the purpose and impact of the changes. Please replace the placeholder template with a proper PR title following the project convention, a concise description explaining what and why the changes were made, a list of relevant tests to ensure coverage, and update the PR checklist to reflect completed items and compliance with repository guidelines.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The PR title accurately follows the repository’s template and concisely summarizes the main change of removing Triton workaround code and simplifying the CUDA 13 installation environment. It clearly references the related JIRA ticket and type, and highlights the primary infrastructure adjustment without extraneous details.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20769 [ run ] triggered by Bot

…ion in CUDA 13 environment

Signed-off-by: ZhanruiSunCh <[email protected]>
Signed-off-by: ZhanruiSunCh <[email protected]>
@ZhanruiSunCh ZhanruiSunCh force-pushed the user/zhanruis/1008_remove_triton_war_code branch from 83d93f7 to ec5b1a5 Compare October 8, 2025 08:02
@ZhanruiSunCh
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20776 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20769 [ run ] completed with state ABORTED
LLM/main/L0_MergeRequest_PR #15697 (Blue Ocean) completed with status: ABORTED

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20776 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #15706 completed with status: 'FAILURE'

@ZhanruiSunCh
Copy link
Collaborator Author

/bot run

Signed-off-by: ZhanruiSunCh <[email protected]>
@ZhanruiSunCh ZhanruiSunCh force-pushed the user/zhanruis/1008_remove_triton_war_code branch from 21f69f9 to d960dc9 Compare October 9, 2025 03:59
@ZhanruiSunCh
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20847 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20849 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20847 [ run ] completed with state ABORTED
LLM/main/L0_MergeRequest_PR #15767 (Blue Ocean) completed with status: ABORTED

@tensorrt-cicd
Copy link
Collaborator

PR_Github #20849 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #15768 completed with status: 'FAILURE'

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