Skip to content

Conversation

@2ez4bz
Copy link
Collaborator

@2ez4bz 2ez4bz commented Jul 29, 2025

Summary by CodeRabbit

  • Bug Fixes

    • Improved output quality for the "mistral3" multimodal model by updating the placement of image placeholders.
    • Updated test expectations for the "mistral-small-3.1-24b-instruct" model to reflect improved keyword accuracy in image-related tasks.
  • Documentation

    • Clarified comments regarding optimal placeholder placement for multimodal models.

[TRTLLM-6598][fix] Switch placement of image placeholder for mistral 3.1

Description

Test Coverage

Ran the following manual tests:

  1. AI2D against trtllm-serve prior to this change: score is around 0.62.
  2. Same as 1, with the change: score is around 0.81.
  3. Same, but against vllm serve in the official 0.9.2 docker image: score is around 0.81.
  4. Same, but hacked the vLLM container to place the [IMG] placeholder token after the text prompt: score is around 0.62.

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.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 29, 2025

📝 Walkthrough

Walkthrough

The changes update the placeholder placement for the "mistral3" multimodal model in a utility file, correcting comments and logic to use a "before text" position based on accuracy tests. Corresponding expected output keywords in an integration test are also updated to reflect these changes. No public interfaces or control flow are modified.

Changes

Cohort / File(s) Change Summary
Model Placeholder Placement Update
tensorrt_llm/inputs/utils.py
Updated the "mistral3" model's placeholder position from AFTER_TEXT to BEFORE_TEXT in the mapping. Revised and expanded comments to clarify rationale and accuracy findings.
Integration Test Keyword Updates
tests/integration/defs/test_e2e.py
Adjusted expected keyword lists for the "mistral-small-3.1-24b-instruct" model under the "image" modality in the test_ptp_quickstart_multimodal test.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • liji-nv
  • venkywonka
  • brb-nv

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1320d8b and 0cadc59.

📒 Files selected for processing (2)
  • tensorrt_llm/inputs/utils.py (1 hunks)
  • tests/integration/defs/test_e2e.py (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • tensorrt_llm/inputs/utils.py
🚧 Files skipped from review as they are similar to previous changes (1)
  • tests/integration/defs/test_e2e.py
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai bot requested review from brb-nv, liji-nv and venkywonka July 29, 2025 06:06
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: 0

🔭 Outside diff range comments (1)
tests/integration/defs/test_e2e.py (1)

2085-2095: Enforce per-list thresholds to avoid unintended tightening

The hard-coded

match_ratio = 4.0/5
if model_name == "qwen2-vl-7b-instruct" and modality == "image":
    match_ratio = 4.0/6

now unintentionally requires ≥6/7 matches (≈85.7%) for the 7-keyword lists. Let’s compute the minimum hits directly per list, preserve the qwen2 special-case, and avoid float comparisons:

-    match_ratio = 4.0 / 5
-    if model_name == "qwen2-vl-7b-instruct" and modality == "image":
-        match_ratio = 4.0 / 6
+    from math import ceil
+
+    # Compute min hits per keyword list:
+    #  - default: ceil(80% of n_keywords)
+    #  - qwen2-vl-7b-instruct + image: require exactly 4
+    def min_required_hits(n_keywords: int, model: str, mode: str) -> int:
+        if model == "qwen2-vl-7b-instruct" and mode == "image":
+            return 4
+        return ceil(0.8 * n_keywords)
 
     for prompt_output, prompt_keywords in zip(
             parse_output(output), expected_keywords[model_name][modality]):
-        matches = [
-            keyword in prompt_output.lower() for keyword in prompt_keywords
-        ]
-        obs_match_ratio = 1. * sum(matches) / len(matches)
-        assert obs_match_ratio >= match_ratio, f"Incorrect output!\nGenerated \"{prompt_output}\"\nExpected keywords \"{prompt_keywords}\"\n Matched keywords: {matches}\n Observed match ratio {obs_match_ratio} below threshold {match_ratio}"
+        matches = [kw in prompt_output.lower() for kw in prompt_keywords]
+        hits = sum(matches)
+        required = min_required_hits(len(prompt_keywords), model_name, modality)
+        assert hits >= required, (
+            f"Incorrect output!\n"
+            f"Generated: \"{prompt_output}\"\n"
+            f"Expected keywords: {prompt_keywords}\n"
+            f"Matched keywords: {matches}\n"
+            f"Required ≥ {required}/{len(prompt_keywords)}, got {hits}"
+        )

• This makes the rule explicit (default ≈80% coverage, one fixed edge case)
Please run CI against all model/modality combinations to confirm no regressions.

🧹 Nitpick comments (1)
tensorrt_llm/inputs/utils.py (1)

257-264: Update the explanatory comment to match the new behaviour

The comment still talks about “does not strictly have to be after the text”, but the mapping directly beneath it now sets mistral3 to BEFORE_TEXT.
Consider revising the phrasing to avoid confusion.

-# NOTE: for mistral3 multimodal models, it does not strictly have to be after the text.
+# NOTE: for mistral3 multimodal models, the placeholder location is not strictly
+# fixed, but accuracy tests show better results when the image precedes the text.
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e11255e and dd07925.

📒 Files selected for processing (2)
  • tensorrt_llm/inputs/utils.py (1 hunks)
  • tests/integration/defs/test_e2e.py (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.py

📄 CodeRabbit Inference Engine (CODING_GUIDELINES.md)

**/*.py: Python code should conform to Python 3.8+.
Indent Python code with 4 spaces. Do not use tabs.
Always maintain the namespace when importing in Python, even if only one class or function from a module is used.
Python filenames should use snake_case (e.g., some_file.py).
Python classes should use PascalCase (e.g., class SomeClass).
Python functions and methods should use snake_case (e.g., def my_awesome_function():).
Python local variables should use snake_case, and prefix k for variable names that start with a number (e.g., k_99th_percentile).
Python global variables should use upper snake_case and prefix G (e.g., G_MY_GLOBAL).
Python constants should use upper snake_case (e.g., MY_CONSTANT).
Avoid shadowing variables declared in an outer scope in Python.
Initialize all externally visible members of a Python class in the constructor.
For interfaces that may be used outside a Python file, prefer docstrings over comments.
Comments in Python should be reserved for code within a function, or interfaces that are local to a file.
Use Google style docstrings for Python classes and functions, which can be parsed by Sphinx.
Attributes and variables in Python can be documented inline; attribute docstrings will be rendered under the docstring for the class.
Avoid using reflection in Python when functionality can be easily achieved without it.
When using try-except blocks in Python, limit the except to the smallest set of errors possible.
When using try-except blocks to handle multiple possible variable types in Python, keep the body of the try as small as possible, using the else block to implement the logic.

Files:

  • tensorrt_llm/inputs/utils.py
  • tests/integration/defs/test_e2e.py
**/*.{cpp,h,hpp,cc,cxx,cu,py}

📄 CodeRabbit Inference Engine (CODING_GUIDELINES.md)

All TensorRT-LLM Open Source Software code should contain an NVIDIA copyright header that includes the current year. This includes .cpp, .h, .cu, .py, and any other source files which are compiled or interpreted.

Files:

  • tensorrt_llm/inputs/utils.py
  • tests/integration/defs/test_e2e.py

@2ez4bz 2ez4bz requested a review from a team as a code owner July 29, 2025 06:22
@2ez4bz
Copy link
Collaborator Author

2ez4bz commented Jul 29, 2025

/bot run --extra-stage "H100_PCIe-PyTorch-Post-Merge-1"

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: 3

🧹 Nitpick comments (2)
tensorrt_llm/_torch/models/checkpoints/hf/weight_loader.py (1)

27-27: Replace debug prints with proper logging.

Debug print statements should use the existing logger instead of print() for consistency with the codebase's logging standards.

-        print(f"==== BEFORE: {len(weight_files)}")
+        logger.debug(f"Safetensors files before filtering: {len(weight_files)}")
-        print(f"==== AFTER: {len(weight_files)}")
+        logger.debug(f"Safetensors files after filtering: {len(weight_files)}")

Also applies to: 29-29

docker/Makefile (1)

165-166: Clean up commented code or document its purpose.

The commented lines suggest work in progress. Either remove them if they're no longer needed or uncomment and configure them properly if they serve a purpose.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dd07925 and 1320d8b.

📒 Files selected for processing (3)
  • docker/Makefile (2 hunks)
  • tensorrt_llm/_torch/models/checkpoints/hf/weight_loader.py (1 hunks)
  • tensorrt_llm/builder.py (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.py

📄 CodeRabbit Inference Engine (CODING_GUIDELINES.md)

**/*.py: Python code should conform to Python 3.8+.
Indent Python code with 4 spaces. Do not use tabs.
Always maintain the namespace when importing in Python, even if only one class or function from a module is used.
Python filenames should use snake_case (e.g., some_file.py).
Python classes should use PascalCase (e.g., class SomeClass).
Python functions and methods should use snake_case (e.g., def my_awesome_function():).
Python local variables should use snake_case, and prefix k for variable names that start with a number (e.g., k_99th_percentile).
Python global variables should use upper snake_case and prefix G (e.g., G_MY_GLOBAL).
Python constants should use upper snake_case (e.g., MY_CONSTANT).
Avoid shadowing variables declared in an outer scope in Python.
Initialize all externally visible members of a Python class in the constructor.
For interfaces that may be used outside a Python file, prefer docstrings over comments.
Comments in Python should be reserved for code within a function, or interfaces that are local to a file.
Use Google style docstrings for Python classes and functions, which can be parsed by Sphinx.
Attributes and variables in Python can be documented inline; attribute docstrings will be rendered under the docstring for the class.
Avoid using reflection in Python when functionality can be easily achieved without it.
When using try-except blocks in Python, limit the except to the smallest set of errors possible.
When using try-except blocks to handle multiple possible variable types in Python, keep the body of the try as small as possible, using the else block to implement the logic.

Files:

  • tensorrt_llm/builder.py
  • tensorrt_llm/_torch/models/checkpoints/hf/weight_loader.py
**/*.{cpp,h,hpp,cc,cxx,cu,py}

📄 CodeRabbit Inference Engine (CODING_GUIDELINES.md)

All TensorRT-LLM Open Source Software code should contain an NVIDIA copyright header that includes the current year. This includes .cpp, .h, .cu, .py, and any other source files which are compiled or interpreted.

Files:

  • tensorrt_llm/builder.py
  • tensorrt_llm/_torch/models/checkpoints/hf/weight_loader.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)
tensorrt_llm/_torch/models/checkpoints/hf/weight_loader.py (1)

28-28: LGTM: Consolidated files filtering is correctly implemented.

The filtering logic to exclude safetensors files containing "consolidated" is appropriate for avoiding duplicate weight loading.

tensorrt_llm/builder.py (1)

688-694: Excellent type safety improvement for kv_cache_type serialization.

The enhanced type checking and explicit error handling ensures robust dictionary conversion. The walrus operator usage is appropriate here for combining assignment and condition checking.

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13314 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

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

@2ez4bz 2ez4bz force-pushed the dev-mistral-fix-acc branch from 1320d8b to 0cadc59 Compare July 29, 2025 16:02
Copy link
Collaborator

@brb-nv brb-nv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@2ez4bz
Copy link
Collaborator Author

2ez4bz commented Jul 29, 2025

/bot run

@2ez4bz
Copy link
Collaborator Author

2ez4bz commented Jul 29, 2025

/bot kill

@2ez4bz
Copy link
Collaborator Author

2ez4bz commented Jul 29, 2025

/bot run --extra-stage "H100_PCIe-PyTorch-Post-Merge-1"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13391 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13392 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13393 [ ] completed with state ABORTED

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13391 [ run ] completed with state ABORTED

@tensorrt-cicd
Copy link
Collaborator

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

@2ez4bz
Copy link
Collaborator Author

2ez4bz commented Jul 29, 2025

/bot run --extra-stage "H100_PCIe-PyTorch-Post-Merge-1"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13398 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

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

@2ez4bz
Copy link
Collaborator Author

2ez4bz commented Jul 29, 2025

/bot run --extra-stage "H100_PCIe-PyTorch-Post-Merge-1"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13408 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

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

@2ez4bz
Copy link
Collaborator Author

2ez4bz commented Jul 30, 2025

/bot run --reuse-test

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13473 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13473 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #10087 completed with status: 'SUCCESS'

@2ez4bz
Copy link
Collaborator Author

2ez4bz commented Jul 30, 2025

first try

@byshiue byshiue merged commit d6eed1b into NVIDIA:main Jul 30, 2025
3 checks passed
lancelly pushed a commit to lancelly/TensorRT-LLM that referenced this pull request Aug 6, 2025
jain-ria pushed a commit to jain-ria/TensorRT-LLM that referenced this pull request Aug 7, 2025
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.

5 participants