Skip to content

Conversation

@lfr-0531
Copy link
Collaborator

@lfr-0531 lfr-0531 commented Nov 23, 2025

Summary by CodeRabbit

  • Chores

    • Updated deepgemm dependency to a newer version.
  • Tests

    • Enhanced test coverage with increased dimensions and sequence lengths for attention mechanisms to ensure robustness across larger model configurations.

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

Description

Optimizations:

  • Larger MMA tile size for the context fp8_mqa_logits kernel
  • MTP-3 support

Fix the failed test in #9349.

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.

@lfr-0531 lfr-0531 requested a review from a team as a code owner November 23, 2025 10:28
@lfr-0531
Copy link
Collaborator Author

/bot run

@lfr-0531 lfr-0531 requested review from chang-l and chzblych November 23, 2025 10:33
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 23, 2025

📝 Walkthrough

Walkthrough

The pull request updates the deepgemm dependency hash in the build configuration to reference the swapab_sm100 branch and increases test dimensionality in DSA indexer tests while adjusting the ke offset calculation.

Changes

Cohort / File(s) Summary
Build dependency update
3rdparty/CMakeLists.txt
Updates deepgemm GIT_TAG from 9fa5965e265e27995f539e0dd73a06351a8a9eaf to 54343662adbc33e9d98704fe9c934fe960129083 with comment referencing swapab_sm100 branch
Test parameter adjustments
tests/unittest/_torch/attention/sparse/test_dsa_indexer.py
Increases num_heads from 32 to 64, seq_len from 512 to 2048, and seq_len_kv from 1024 to 4096 in deepgemm FP8 MQA tests; removes +1 offset from ke calculation to align with seq_len_kv - seq_len

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

  • CMakeLists update is a straightforward dependency version bump
  • Test modifications follow a consistent pattern across both FP8 MQA test blocks
  • ke calculation change warrants verification that the new formula (without +1) is correct for the updated test dimensions

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The description includes optimization details and test fixes but is missing the Test Coverage section that lists relevant safeguarding tests as required by the template. Complete the Test Coverage section by explicitly listing which tests safeguard the changes (e.g., test_dsa_indexer.py test cases).
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: updating DeepGEMM to a latest commit with optimizations for DeepSeek-v3.2, matching the PR's primary objective.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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

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

📜 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 1ef69ec and cd2149a.

📒 Files selected for processing (2)
  • 3rdparty/CMakeLists.txt (1 hunks)
  • tests/unittest/_torch/attention/sparse/test_dsa_indexer.py (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-08-14T21:04:50.248Z
Learnt from: thorjohnsen
Repo: NVIDIA/TensorRT-LLM PR: 6910
File: cpp/tensorrt_llm/batch_manager/kvCacheManager.cpp:0-0
Timestamp: 2025-08-14T21:04:50.248Z
Learning: In KV cache onboarding logic during prefill in cpp/tensorrt_llm/batch_manager/kvCacheManager.cpp, when calculating which blocks fall within the attention window, use getTokensPerBlock() to advance token indices rather than block->getUniqueTokens().size(), because the calculation needs to consider the post-prefill state where blocks will be filled to capacity, not their current token count.

Applied to files:

  • tests/unittest/_torch/attention/sparse/test_dsa_indexer.py
📚 Learning: 2025-09-29T15:14:28.503Z
Learnt from: amitz-nv
Repo: NVIDIA/TensorRT-LLM PR: 8063
File: tensorrt_llm/lora_manager.py:1080-1112
Timestamp: 2025-09-29T15:14:28.503Z
Learning: In tensorrt_llm/lora_manager.py, when calculating part_sizes for attn_qkv fused LoRA modules, the sizes are correctly multiplied by tp_size because model_config.num_heads and model_config.num_kv_heads are already divided by tp_size (per-TP-rank values), so multiplication is needed to get the original full concatenated dimension size. The interleave_fused_lora_weights_for_tp function provides proper validation with asserts for total size and TP divisibility.

Applied to files:

  • tests/unittest/_torch/attention/sparse/test_dsa_indexer.py
⏰ 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 (1)

42-42: LGTM! DeepGEMM dependency update looks good.

The commit hash update to include DeepSeek-v3.2 optimizations is appropriately documented with the branch reference.

tests/unittest/_torch/attention/sparse/test_dsa_indexer.py (1)

311-313: LGTM! Test dimension increases align with DeepGEMM optimizations.

The larger test dimensions (num_heads: 32→64, seq_len: 512→2048, seq_len_kv: 1024→4096) appropriately validate the new larger MMA tile size optimizations mentioned in the PR objectives.

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25446 [ run ] triggered by Bot. Commit: 55f1cd8

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25446 [ run ] completed with state FAILURE. Commit: 55f1cd8
/LLM/main/L0_MergeRequest_PR pipeline #19260 completed with status: 'FAILURE'

@lfr-0531
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25457 [ run ] triggered by Bot. Commit: 55f1cd8

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25457 [ run ] completed with state SUCCESS. Commit: 55f1cd8
/LLM/main/L0_MergeRequest_PR pipeline #19271 completed with status: 'FAILURE'

@lfr-0531
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25504 [ run ] triggered by Bot. Commit: 87d46ea

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25504 [ run ] completed with state FAILURE. Commit: 87d46ea
/LLM/main/L0_MergeRequest_PR pipeline #19314 completed with status: 'ABORTED'

Signed-off-by: Fanrong Li <23290157+lfr-0531@users.noreply.github.com>
Signed-off-by: Fanrong Li <23290157+lfr-0531@users.noreply.github.com>
@lfr-0531 lfr-0531 force-pushed the user/fanrongl/update_dg branch from 87d46ea to 06688eb Compare November 24, 2025 07:46
@lfr-0531
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25519 [ run ] triggered by Bot. Commit: 06688eb

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25519 [ run ] completed with state SUCCESS. Commit: 06688eb
/LLM/main/L0_MergeRequest_PR pipeline #19325 completed with status: 'FAILURE'

@lfr-0531
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25544 [ run ] triggered by Bot. Commit: 06688eb

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25544 [ run ] completed with state SUCCESS. Commit: 06688eb
/LLM/main/L0_MergeRequest_PR pipeline #19343 completed with status: 'FAILURE'

@lfr-0531
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25573 [ run ] triggered by Bot. Commit: 06688eb

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25573 [ run ] completed with state SUCCESS. Commit: 06688eb
/LLM/main/L0_MergeRequest_PR pipeline #19370 completed with status: 'SUCCESS'
Pipeline passed with automatic retried tests. Check the rerun report for details.

@lfr-0531 lfr-0531 enabled auto-merge (squash) November 25, 2025 00:33
@lfr-0531 lfr-0531 merged commit 5a99c97 into NVIDIA:main Nov 25, 2025
5 checks passed
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.

3 participants