Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

[https://nvbugs/5519525][fix] fix doc invalid link for bug 5519525#7753

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

@nv-guomingz
Copy link
Collaborator

@nv-guomingznv-guomingz commentedSep 16, 2025•
edited by coderabbitaibot
Loading

Summary by CodeRabbit

  • Documentation
    • Updated links to the TensorRT-Model-Optimizer deployment docs.
    • Expanded PyTorch quantization guidance with a sample hf_quant_config.json, KV-cache quantization behavior, mapping table, and examples.
    • Added instructions to force KV-cache dtype via YAML (kv_cache_dtype) and documented valid values (auto, fp8).
    • Clarified phrasing and added example YAML snippets and notes to aid configuration.

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 FollowsTRT-LLM CODING GUIDELINES to the best of your knowledge.

  • Test cases are provided for new code paths (seetest 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: DoesNOT update GitHub check status.

--stage-list "A10-PyTorch-1, xxx"(OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-1, xxx". Note: DoesNOT 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: DoesNOT 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: DoesNOT update GitHub pipeline status.

--only-multi-gpu-test(OPTIONAL) : Only run the multi-GPU tests. Note: DoesNOT update GitHub check status.

--disable-multi-gpu-test(OPTIONAL) : Disable the multi-GPU tests. Note: DoesNOT 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-list parameter to access the appropriate container environment. Note: DoesNOT update GitHub check status.

For guidance on mapping tests to stage names, seedocs/source/reference/ci-overview.md
and thescripts/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.

@nv-guomingznv-guomingz requested a review froma team as acode ownerSeptember 16, 2025 05:55
@nv-guomingznv-guomingz added Release BlockerPRs that blocking the final release build or branching out the release branch 1.0_doc labelsSep 16, 2025
@coderabbitai
Copy link
Contributor

coderabbitaibot commentedSep 16, 2025•
edited
Loading

📝 Walkthrough

Walkthrough

Updated perf-benchmarking documentation: replaced two TensorRT Model Optimizer links and expanded the PyTorch quantization section with hf_quant_config.json schema, kv_cache_quant_algo behavior, trtllm-bench KV-cache-selection logic, a behavior matrix, and a YAML kv_cache_dtype override example plus valid values.

Changes

Cohort / File(s)Summary
Docs: Perf benchmarking and quantization
docs/source/developer-guide/perf-benchmarking.md		Replaced two TensorRT Model Optimizer URLs with the TensorRT-LLM deployment page; expanded PyTorch flow quantization guidance including samplehf_quant_config.json structure,kv_cache_quant_algo, and howtrtllm-bench chooses KV-cache quantization; added mapping of compute vs KV-cache decisions, YAMLkv_cache_dtype override example and valid values (auto,fp8); minor wording edits.

Sequence Diagram(s)

sequenceDiagram  autonumber  participant U as User  participant TB as trtllm-bench  participant CKPT as Checkpoint (hf_quant_config.json)  participant CFG as YAML Config  Note over U,TB: Run benchmark in PyTorch flow  U->>TB: Invoke benchmark  TB->>CKPT: Read hf_quant_config.json  CKPT-->>TB: Return compute_quant, kv_cache_quant_algo  TB->>CFG: Read kv_cache_dtype (if present)  alt YAML kv_cache_dtype provided    TB->>TB: Force KV-cache dtype per YAML (auto | fp8)  else No YAML override    TB->>TB: Determine KV-cache quant using compute_quant + kv_cache_quant_algo rules  end  TB-->>U: Start benchmark with selected compute & KV-cache quantization
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check nameStatusExplanationResolution
Description Check⚠️ WarningThe PR body is just the repository template and placeholder text without a filled "Description" or "Test Coverage" and therefore does not explain what was changed, why, or how it was verified; it lacks the concrete details (files changed, the exact broken link, verification steps) reviewers need to validate the fix. Although the PR metadata and raw_summary indicate a documentation link was corrected for NVBugs 5519525, that context is not present in the PR description itself, making the description incomplete for review. This omission also prevents automated reviewers or maintainers from quickly assessing test impact and whether CI can be skipped.Please update the PR description by replacing the template placeholders with a concise Description that lists the modified file(s) and the exact link fixed (including the NVBugs ID), a Test Coverage section describing how the change was verified, and any CI notes (e.g., "docs only change" / bot command already used); also confirm the PR checklist items relevant to docs updates.
✅ Passed checks (2 passed)
Check nameStatusExplanation
Title Check✅ PassedThe title follows the repository ticket/type template and clearly identifies the NVBugs ID and the purpose of the change (fixing an invalid documentation link), succinctly summarizing the primary intent for reviewers. It is specific and directly related to the changes described in the PR metadata.
Docstring Coverage✅ PassedNo functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see thedocumentation for more information.

Example:

reviews:pre_merge_checks:custom_checks:      -name:"Undocumented Breaking Changes"mode:"warning"instructions:|          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on thisDiscord post.

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.

@nv-guomingz
Copy link
CollaboratorAuthor

/bot skip --comments "docs only change"

Copy link
Contributor

@coderabbitaicoderabbitaibot 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: 0

🧹 Nitpick comments (2)
docs/source/developer-guide/perf-benchmarking.md (2)

447-449:Nit: fix punctuation in this sentence.

Change “When runningtrtllm-bench throughput. The benchmark will …” to a single sentence.

-When running `trtllm-bench throughput`. The benchmark will select a KV cache quantization ...+When running `trtllm-bench throughput`, the benchmark will select a KV cache quantization ...

428-444:Optional: add a cross‑reference to the hf_quant_config.json schema.

After introducinghf_quant_config.json, link to the ModelOpt “Unified HuggingFace Checkpoint” page that documents this file and its fields (quantization.quant_algo,quantization.kv_cache_quant_algo). This will help readers align expectations across frameworks. (nvidia.github.io)

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between7df515e andcb3b4af.

📒 Files selected for processing (1)
  • docs/source/developer-guide/perf-benchmarking.md (1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📚 Learning: 2025-09-09T09:40:45.658Z
Learnt from: fredricz-20070104PR: NVIDIA/TensorRT-LLM#7645File: tests/integration/test_lists/qa/llm_function_core.txt:648-648Timestamp: 2025-09-09T09:40:45.658ZLearning: In TensorRT-LLM test lists, it's common and intentional for the same test to appear in multiple test list files when they serve different purposes (e.g., llm_function_core.txt for comprehensive core functionality testing and llm_function_core_sanity.txt for quick sanity checks). This duplication allows tests to be run in different testing contexts.

Applied to files:

  • docs/source/developer-guide/perf-benchmarking.md
📚 Learning: 2025-08-06T13:58:07.506Z
Learnt from: galagamPR: NVIDIA/TensorRT-LLM#6487File: tests/unittest/_torch/auto_deploy/unit/singlegpu/test_ad_trtllm_bench.py:1-12Timestamp: 2025-08-06T13:58:07.506ZLearning: In TensorRT-LLM, test files (files under tests/ directories) do not require NVIDIA copyright headers, unlike production source code files. Test files typically start directly with imports, docstrings, or code.

Applied to files:

  • docs/source/developer-guide/perf-benchmarking.md
📚 Learning: 2025-07-28T17:06:08.621Z
Learnt from: moraxuPR: NVIDIA/TensorRT-LLM#6303File: tests/integration/test_lists/qa/examples_test_list.txt:494-494Timestamp: 2025-07-28T17:06:08.621ZLearning: In TensorRT-LLM testing, it's common to have both CLI flow tests (test_cli_flow.py) and PyTorch API tests (test_llm_api_pytorch.py) for the same model. These serve different purposes: CLI flow tests validate the traditional command-line workflow, while PyTorch API tests validate the newer LLM API backend. Both are legitimate and should coexist.

Applied to files:

  • docs/source/developer-guide/perf-benchmarking.md
⏰ 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 (1)
docs/source/developer-guide/perf-benchmarking.md (1)

426-426:Good fix: updated ModelOpt doc link is valid and points to the TensorRT‑LLM deployment section.

The new URL resolves and is the right target for exporting/using quantized checkpoints with TensorRT‑LLM. (nvidia.github.io)

@nv-guomingznv-guomingzenabled auto-merge (squash)September 16, 2025 05:58
@tensorrt-cicd
Copy link
Collaborator

PR_Github #18725 Bot args parsing error: usage: /bot skip --comment COMMENT
/bot skip: error: the following arguments are required: --comment

Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>
@nv-guomingznv-guomingzforce-pushed theuser/guomingz/fix_nvbug_5519525 branch fromcb3b4af tob53a264CompareSeptember 16, 2025 08:04
@nv-guomingz
Copy link
CollaboratorAuthor

/bot skip --comment "docs only change"

Copy link
Contributor

@coderabbitaicoderabbitaibot 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: 0

🧹 Nitpick comments (1)
docs/source/developer-guide/perf-benchmarking.md (1)

446-449:Grammar/flow nit: fix subordinate clause sentence.

“When runningtrtllm-bench throughput. The benchmark …” is ungrammatical. Merge into a single sentence.

-When running `trtllm-bench throughput`. The benchmark will select a KV cache quantization that is best suited-for the compute precision in the checkpoint automatically if `kv_cache_quant_algo` is specified as `null`, otherwise it will-be forced to match the specified non-null KV cache quantization. The following are the mappings that `trtllm-bench` will-follow when a checkpoint does not specify a KV cache quantization algorithm:+When running `trtllm-bench throughput`, the benchmark automatically selects a KV‑cache quantization best suited+to the checkpoint’s compute precision if `kv_cache_quant_algo` is `null`; otherwise, it uses the specified non‑null+KV‑cache quantization. The following mappings apply when a checkpoint does not specify a KV‑cache quantization algorithm:
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and betweencb3b4af andb53a264.

📒 Files selected for processing (1)
  • docs/source/developer-guide/perf-benchmarking.md (1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📚 Learning: 2025-09-09T09:40:45.658Z
Learnt from: fredricz-20070104PR: NVIDIA/TensorRT-LLM#7645File: tests/integration/test_lists/qa/llm_function_core.txt:648-648Timestamp: 2025-09-09T09:40:45.658ZLearning: In TensorRT-LLM test lists, it's common and intentional for the same test to appear in multiple test list files when they serve different purposes (e.g., llm_function_core.txt for comprehensive core functionality testing and llm_function_core_sanity.txt for quick sanity checks). This duplication allows tests to be run in different testing contexts.

Applied to files:

  • docs/source/developer-guide/perf-benchmarking.md
📚 Learning: 2025-08-06T13:58:07.506Z
Learnt from: galagamPR: NVIDIA/TensorRT-LLM#6487File: tests/unittest/_torch/auto_deploy/unit/singlegpu/test_ad_trtllm_bench.py:1-12Timestamp: 2025-08-06T13:58:07.506ZLearning: In TensorRT-LLM, test files (files under tests/ directories) do not require NVIDIA copyright headers, unlike production source code files. Test files typically start directly with imports, docstrings, or code.

Applied to files:

  • docs/source/developer-guide/perf-benchmarking.md
📚 Learning: 2025-07-28T17:06:08.621Z
Learnt from: moraxuPR: NVIDIA/TensorRT-LLM#6303File: tests/integration/test_lists/qa/examples_test_list.txt:494-494Timestamp: 2025-07-28T17:06:08.621ZLearning: In TensorRT-LLM testing, it's common to have both CLI flow tests (test_cli_flow.py) and PyTorch API tests (test_llm_api_pytorch.py) for the same model. These serve different purposes: CLI flow tests validate the traditional command-line workflow, while PyTorch API tests validate the newer LLM API backend. Both are legitimate and should coexist.

Applied to files:

  • docs/source/developer-guide/perf-benchmarking.md
⏰ 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)
docs/source/developer-guide/perf-benchmarking.md (2)

426-426:AI summary appears broader than the actual diff.

The AI summary mentions multiple link replacements and added quantization guidance, but the provided diff only shows this single link update. Confirm whether other intended doc edits were already merged elsewhere or should be included here.

426-426:Linkcheck passed — external doc URL returns 200 OK. Verified with curl:https://nvidia.github.io/TensorRT-Model-Optimizer/deployment/1_tensorrt_llm.html -> 200 (no redirect).

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18748 [ skip ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18748 [ skip ] completed with stateSUCCESS
Skipping testing for commitb53a264

@nv-guomingznv-guomingz merged commit64f7cca intoNVIDIA:release/1.0Sep 16, 2025
5 checks passed
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 16, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 16, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 16, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 16, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 17, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 17, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 17, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 17, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 17, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 17, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 17, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 18, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 18, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 18, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 19, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 19, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 19, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
dominicshanshan pushed a commit to dominicshanshan/TensorRT-LLM that referenced this pull requestSep 19, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
chzblych pushed a commit that referenced this pull requestSep 22, 2025
…7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
JunyiXu-nv pushed a commit to JunyiXu-nv/TensorRT-LLM that referenced this pull requestSep 22, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
nv-lschneider pushed a commit to nv-lschneider/TensorRT-LLM that referenced this pull requestSep 22, 2025
…VIDIA#7753)Signed-off-by: nv-guomingz <137257613+nv-guomingz@users.noreply.github.com>Signed-off-by: Wangshanshan <30051912+dominicshanshan@users.noreply.github.com>
@nv-guomingznv-guomingz deleted the user/guomingz/fix_nvbug_5519525 branchSeptember 30, 2025 07:45
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@coderabbitaicoderabbitai[bot]coderabbitai[bot] left review comments

@chzblychchzblychchzblych approved these changes

Assignees

No one assigned

Labels

Release BlockerPRs that blocking the final release build or branching out the release branch

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@nv-guomingz@tensorrt-cicd@chzblych
[8]ページ先頭
©2009-2025 Movatter.jp