[None][fix] Update DeepGEMM dependency to the latest commit

[chzblych]

Summary by CodeRabbit

• Chores
  • Updated internal dependencies to latest compatible versions.

_{✏️ 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.

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.

[chzblych]

/bot run --skip-test

[coderabbitai]

📝 Walkthrough

Walkthrough

The change updates the DeepGEMM dependency Git tag in the 3rdparty build configuration from one commit to another, targeting the swapab_sm100 branch. No control flow or logic modifications are present.

Changes

Cohort / File(s)	Summary
Dependency version update 3rdparty/CMakeLists.txt	Updated DeepGEMM FetchContent_Declare GIT_TAG from 9fa5965e265e27995f539e0dd73a06351a8a9eaf to 54343662adbc33e9d98704fe9c934fe960129083 with swapab_sm100 branch comment

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is empty except for the template boilerplate; it lacks the actual description, test coverage details, and explanation of the update rationale.	Add a meaningful description explaining why the DeepGEMM update is needed, what issues it fixes, and document relevant test coverage for the change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: updating the DeepGEMM dependency to a specific commit, which aligns with the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b5863ed and 1950ef1.

📒 Files selected for processing (1)

• 3rdparty/CMakeLists.txt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Pre-commit Check

🔇 Additional comments (2)

3rdparty/CMakeLists.txt (2)

42-42: Verified: Commit is valid and part of the swapab_sm100 branch.

The commit SHA 54343662adbc33e9d98704fe9c934fe960129083 exists and is the current HEAD of the swapab_sm100 branch. The code change is sound.

---

39-44: Based on my verification, the review comment remains valid. The web search found a similar case in TensorRT-LLM PR #7875 where a DeepGEMM commit SHA returned a GitHub API 404 error, indicating this is a known pattern with DeepGEMM updates. I could not find specific information about commit 54343662adbc33e9d98704fe9c934fe960129083 or the swapab_sm100 branch in public repositories.

---

Insufficient PR context for this dependency update.

The PR description lacks detail on why this DeepGEMM dependency update is needed. No information is provided about what functionality or fixes the new commit introduces, or whether it has been tested for compatibility with the current TensorRT-LLM codebase.

Please clarify:

• What changes or fixes does the new commit (54343662...) introduce?
• Has this change been tested to ensure compatibility?
• Are there any breaking changes or behavioral differences compared to the previous version?

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[tensorrt-cicd]

PR_Github #25286 [ run ] triggered by Bot. Commit: 1950ef1

[ruoqianguo]

/bot run

[tensorrt-cicd]

PR_Github #25336 [ run ] triggered by Bot. Commit: 1950ef1

[tensorrt-cicd]

PR_Github #25286 [ run ] completed with state ABORTED. Commit: 1950ef1

[tensorrt-cicd]

PR_Github #25336 [ run ] completed with state SUCCESS. Commit: 1950ef1
/LLM/main/L0_MergeRequest_PR pipeline #19164 completed with status: 'FAILURE'

[lfr-0531]

/bot run

[tensorrt-cicd]

PR_Github #25360 [ run ] triggered by Bot. Commit: 1950ef1

[tensorrt-cicd]

PR_Github #25360 [ run ] completed with state SUCCESS. Commit: 1950ef1
/LLM/main/L0_MergeRequest_PR pipeline #19181 completed with status: 'FAILURE'

[chzblych]

Closed in favor of #9380.