Skip to content

Conversation

@pengbowang-nv
Copy link
Collaborator

@pengbowang-nv pengbowang-nv commented Aug 4, 2025

Summary by CodeRabbit

  • New Features
    • Added support and accuracy references for the moonshotai/Kimi-K2-Instruct model with FP8 block scales quantization.
  • Tests
    • Introduced new integration tests for the moonshotai/Kimi-K2-Instruct model, including accuracy and latency checks.
  • Bug Fixes
    • Improved tokenizer backend selection for incremental decoding to handle cases where certain tokenizer attributes are missing.
  • Chores
    • Added the blobfile package as a new dependency.

Description

Modify incremental detokenization for models that doesn't have fast tokenizer impl (affecting kimi k2).

Add blobfile as a dependency required by the tokenizer of Kimi-K2.

Add Kimi-K2 model MMLU and GSM8K test to safeguard accuracy. The test is also added to QA test list.

Test Coverage

test_llm_api_pytorch.py::TestKimiK2::test_fp8_blockscale[latency]

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 Aug 4, 2025

📝 Walkthrough

Walkthrough

A new model, moonshotai/Kimi-K2-Instruct, is integrated into the accuracy reference YAMLs and tested for FP8_BLOCK_SCALES quantization in PyTorch LLM API tests. The tokenizer selection logic is updated to check for a specific attribute. The blobfile dependency is added, and a new test entry is included in the QA test list.

Changes

Cohort / File(s) Change Summary
Dependency Update
requirements.txt
Added the blobfile package as a new dependency.
Accuracy Reference: Kimi-K2 Model
tests/integration/defs/accuracy/references/gsm8k.yaml, tests/integration/defs/accuracy/references/mmlu.yaml
Added new entries for the moonshotai/Kimi-K2-Instruct model with FP8_BLOCK_SCALES quantization and specified accuracy values to the GSM8K and MMLU accuracy reference YAML files.
PyTorch LLM API Test: Kimi-K2
tests/integration/defs/accuracy/test_llm_api_pytorch.py
Introduced a new test class, TestKimiK2, to test the moonshotai/Kimi-K2-Instruct model with FP8_BLOCK_SCALES quantization, including a parameterized test method and relevant configuration.
Tokenizer Backend Logic
tensorrt_llm/llmapi/tokenizer.py
Enhanced the backend selection logic in TransformersTokenizer.decode_incrementally to check for the presence of the _tokenizer attribute on the tokenizer object, affecting which incremental decoding backend is used.
QA Test List Update
tests/integration/test_lists/qa/llm_function_sanity.txt
Added a new entry for the TestKimiK2::test_fp8_blockscale[latency] test to the QA test list.

Sequence Diagram(s)

sequenceDiagram
    participant TestRunner
    participant TestKimiK2
    participant LLM
    participant Tokenizer

    TestRunner->>TestKimiK2: Run test_fp8_blockscale(...)
    TestKimiK2->>LLM: Instantiate with FP8_BLOCK_SCALES quantization
    LLM->>Tokenizer: decode_incrementally(...)
    Tokenizer->>Tokenizer: Check _tokenizer attribute
    alt Has _tokenizer
        Tokenizer->>Tokenizer: Use hf_decode_incrementally
    else
        Tokenizer->>Tokenizer: Use trtllm_decode_incrementally
    end
    TestKimiK2->>LLM: Evaluate MMLU and GSM8K tasks
    LLM-->>TestKimiK2: Return evaluation results
    TestKimiK2-->>TestRunner: Assert quant_algo and test results
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

  • tests: Add llama4 functional cases #6392: Adds new functional tests for llama4 models with FP8 and FP4 quantization, modifying similar accuracy test files and test classes as this PR, but for different models and quantization schemes.

Suggested labels

Community want to contribute

Suggested reviewers

  • litaotju
  • yilin-void
  • syuoni
  • LarryXFly

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 70be182 and 9497b60.

📒 Files selected for processing (6)
  • requirements.txt (1 hunks)
  • tensorrt_llm/llmapi/tokenizer.py (1 hunks)
  • tests/integration/defs/accuracy/references/gsm8k.yaml (1 hunks)
  • tests/integration/defs/accuracy/references/mmlu.yaml (1 hunks)
  • tests/integration/defs/accuracy/test_llm_api_pytorch.py (1 hunks)
  • tests/integration/test_lists/qa/llm_function_sanity.txt (1 hunks)
✅ Files skipped from review due to trivial changes (3)
  • tensorrt_llm/llmapi/tokenizer.py
  • tests/integration/test_lists/qa/llm_function_sanity.txt
  • tests/integration/defs/accuracy/references/gsm8k.yaml
🚧 Files skipped from review as they are similar to previous changes (3)
  • requirements.txt
  • tests/integration/defs/accuracy/references/mmlu.yaml
  • tests/integration/defs/accuracy/test_llm_api_pytorch.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
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • 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
🪧 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.
  • 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.

Support

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

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.

@pengbowang-nv
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13938 [ run ] triggered by Bot

@yizhang-nv yizhang-nv requested review from litaotju and xinhe-nv August 4, 2025 06:06
@tensorrt-cicd
Copy link
Collaborator

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

@pengbowang-nv pengbowang-nv requested a review from a team as a code owner August 4, 2025 07:28
@pengbowang-nv pengbowang-nv requested a review from Superjomn August 4, 2025 07:28
@pengbowang-nv pengbowang-nv changed the title [None][chore] Add test and dependency for Kimi-K2 [None][fix] fix kimi k2 serving and add test for Kimi-K2 Aug 4, 2025
@pengbowang-nv
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #14062 [ run ] triggered by Bot

Copy link
Collaborator

@Superjomn Superjomn left a comment

Choose a reason for hiding this comment

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

LGTM from the llmapi perspective

@tensorrt-cicd
Copy link
Collaborator

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

@pengbowang-nv
Copy link
Collaborator Author

/bot reuse-pipeline

@tensorrt-cicd
Copy link
Collaborator

PR_Github #14132 [ reuse-pipeline ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #14132 [ reuse-pipeline ] completed with state SUCCESS
Reusing PR_Github #14062 for commit 9497b60

@litaotju litaotju merged commit c289880 into NVIDIA:main Aug 5, 2025
5 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
@pengbowang-nv pengbowang-nv deleted the dev-add-kimi-k2-test branch September 2, 2025 09:29
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.

4 participants