Skip to content

Conversation

LinPoly
Copy link
Collaborator

@LinPoly LinPoly commented Oct 10, 2025

Summary by CodeRabbit

  • New Features

    • Added support to configure the tokenizer via the TOKENIZER_PATH_OR_NAME environment variable, allowing use of either a local tokenizer directory or a hosted model name.
    • Applies to both text and multimodal performance client scripts, replacing previously hard-coded tokenizer values.
  • Documentation

    • Added inline comments explaining how to set and use TOKENIZER_PATH_OR_NAME for customizing the tokenizer source.

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.

Signed-off-by: Pengyun Lin <[email protected]>
@LinPoly LinPoly requested a review from JunyiXu-nv October 10, 2025 09:02
@LinPoly LinPoly requested a review from a team as a code owner October 10, 2025 09:02
@LinPoly LinPoly changed the title Use local tokenizer [https://nvbugs/5546197][fix] Use local tokenizer Oct 10, 2025
Copy link
Contributor

coderabbitai bot commented Oct 10, 2025

📝 Walkthrough

Walkthrough

Two perf client shell scripts were updated to replace hard-coded tokenizer names with a TOKENIZER_PATH_OR_NAME variable, defaulting to a local path or allowing an environment override. Comments explaining the variable were added. No other options or control flow were changed.

Changes

Cohort / File(s) Summary of Changes
Perf client scripts
examples/serve/genai_perf_client.sh, examples/serve/genai_perf_client_for_multimodal.sh
Replaced hard-coded --tokenizer values with --tokenizer $TOKENIZER_PATH_OR_NAME. Introduced TOKENIZER_PATH_OR_NAME variable with default local path and comments. All other command options and script flow unchanged.

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 is still the default template with placeholder comments and lacks any actual content such as a formatted title, a filled Description section, a Test Coverage section, or updates to the PR Checklist. Please replace the template placeholders with real content by providing a PR title using the “[ticket][type] Summary” format, writing a concise description of the issue and the changes made, listing relevant tests under Test Coverage, and marking completed items in the PR Checklist.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The title “[https://nvbugs/5546197][fix] Use local tokenizer” correctly follows the required ticket format and clearly summarizes the primary change of enabling a local tokenizer, matching the modifications in the scripts. It is concise, specific to the main update, and understandable at a glance.
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.

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

🧹 Nitpick comments (4)
examples/serve/genai_perf_client_for_multimodal.sh (2)

3-5: Make default env-override friendly

Use parameter expansion so a pre-set TOKENIZER_PATH_OR_NAME is respected; keep default as fallback.

-TOKENIZER_PATH_OR_NAME="/scratch.trt_llm_data/llm-models/Qwen2.5-VL-3B-Instruct"
+TOKENIZER_PATH_OR_NAME="${TOKENIZER_PATH_OR_NAME:-/scratch.trt_llm_data/llm-models/Qwen2.5-VL-3B-Instruct}"

8-8: Quote tokenizer path/name

Protects paths with spaces and special chars.

-    --tokenizer $TOKENIZER_PATH_OR_NAME \
+    --tokenizer "${TOKENIZER_PATH_OR_NAME}" \
examples/serve/genai_perf_client.sh (2)

3-5: Respect pre-set TOKENIZER_PATH_OR_NAME

Allow environment override with a fallback default.

-TOKENIZER_PATH_OR_NAME="/scratch.trt_llm_data/llm-models/llama-models-v2/TinyLlama-1.1B-Chat-v1.0"
+TOKENIZER_PATH_OR_NAME="${TOKENIZER_PATH_OR_NAME:-/scratch.trt_llm_data/llm-models/llama-models-v2/TinyLlama-1.1B-Chat-v1.0}"

8-8: Quote expansion for safety

Prevents word splitting/globbing if the value contains spaces.

-    --tokenizer $TOKENIZER_PATH_OR_NAME \
+    --tokenizer "${TOKENIZER_PATH_OR_NAME}" \
📜 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 f720582 and a1c8c58.

📒 Files selected for processing (2)
  • examples/serve/genai_perf_client.sh (1 hunks)
  • examples/serve/genai_perf_client_for_multimodal.sh (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). (2)
  • GitHub Check: Check PR Checklist Resolution
  • GitHub Check: Pre-commit Check

@LinPoly
Copy link
Collaborator Author

LinPoly commented Oct 10, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #21016 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #21016 [ run ] completed with state SUCCESS
/LLM/release-1.1/L0_MergeRequest_PR pipeline #76 completed with status: 'SUCCESS'

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