Skip to content

Conversation

@pcastonguay
Copy link
Collaborator

@pcastonguay pcastonguay commented Aug 18, 2025

Summary by CodeRabbit

  • Tests
    • Re-enabled KV-cache event tests that were previously skipped to improve coverage.
    • Updated validations to avoid fixed event_id assumptions; now validate created vs stored semantics and ensure stored events have positive IDs.
    • Accumulate and assert per-batch stored block counts (5 blocks after each batch) and verify removal events between batches.
    • Confirm final absence of events; no public API/signature changes.

Description

Test Coverage

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: Patrice Castonguay <[email protected]>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 18, 2025

📝 Walkthrough

Walkthrough

Re-enabled and adjusted kv-cache events tests: removed explicit pytest skips and refactored event validation to avoid fixed event_id checks, accumulate stored blocks, detect removal events across batches, and special-case attention-dataplane paths. No public API/signature changes.

Changes

Cohort / File(s) Summary
Tests
tests/unittest/llmapi/test_llm_kv_cache_events.py
- Removed explicit pytest skip decorators for test_llm_kv_events_api and test_llm_api_attention_dp_kv_events.
- Reworked check_events to avoid fixed event_id expectations; introduced total_stored_blocks accumulation and has_removed_event detection across request batches.
- For non-attention DP paths: require stored events event_id > 0, created events event_id == 0, accumulate blocks.
- For attention-dataplane ranks: validate by type ("created"/"stored"), enforce created→event_id == 0, stored→event_id > 0, accumulate blocks, and skip absent events safely.
- Between batches detect removals via type == "removed" and validate block_hashes; assert total_stored_blocks == 5 after each batch and no events remain after final request.
- No public API/signature changes.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

Suggested reviewers

  • chzblych
  • Tabrizian
  • yiqingy0

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ 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.
    • 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.
  • 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 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/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

@pcastonguay
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #15629 [ run ] triggered by Bot

@pcastonguay pcastonguay changed the title [nvbug 5444937][chore] Unwaiving KV events test [nvbugs 5444937, 5451407][chore] Fixing KV events tests Aug 18, 2025
@pcastonguay
Copy link
Collaborator Author

/bot run --disable-fail-fast

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

🔭 Outside diff range comments (1)
tests/unittest/llmapi/test_llm_kv_cache_events.py (1)

1-3: Add NVIDIA copyright header to Python test file

Per repo guidelines, prepend the standard NVIDIA header (current year) to all source files. For this test, use:

+# Copyright 2025, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+
 import asyncio
 import time

• tests/unittest/llmapi/test_llm_kv_cache_events.py: insert header above the first import.

🧹 Nitpick comments (3)
tests/unittest/llmapi/test_llm_kv_cache_events.py (3)

187-187: Avoid hard-coding total_stored_blocks == 5; make the assertion resilient

The exact number of blocks can depend on tokens-per-block, model config, and runtime heuristics. Asserting equality to 5 is brittle and may flake across environments.

Consider relaxing to a minimal guarantee, or compute the expectation from configuration if available:

-    assert total_stored_blocks == 5  # Should have 5 blocks in total
+    assert total_stored_blocks > 0, f"Expected at least 1 stored block, got {total_stored_blocks}"

If there is a stable way to infer expected blocks (e.g., from llm.kv_cache_config.tokens_per_block and request length), prefer computing it and asserting equality.


195-209: Second batch checks: relax block count equality; keep removed-event check

Great to verify a "removed" event between batches. However, asserting total_stored_blocks == 5 is likely to be environment-dependent.

Apply:

-    assert total_stored_blocks == 5  # Should have 5 blocks in total
+    assert total_stored_blocks > 0, f"Expected some stored blocks after second batch, got {total_stored_blocks}"
     assert has_removed_event

Optionally, gate the removed-event assertion on block reuse being enabled if that configuration can vary:

  • Only assert has_removed_event if block reuse is enabled in the active kv_cache_config.

217-231: Third batch checks: same resilience for block counts

Mirror the relaxation applied to the second batch to avoid brittleness.

Apply:

-    assert total_stored_blocks == 5  # Should have 5 blocks in total
+    assert total_stored_blocks > 0, f"Expected some stored blocks after third batch, got {total_stored_blocks}"
     assert has_removed_event
📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between bbc2f37 and 9c67018.

📒 Files selected for processing (1)
  • tests/unittest/llmapi/test_llm_kv_cache_events.py (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.py

📄 CodeRabbit Inference Engine (CODING_GUIDELINES.md)

**/*.py: Python code must target Python 3.8+
Python indentation: 4 spaces, no tabs
Maintain module namespace in imports (from package.subpackage import foo; then use foo.SomeClass())
Python file names use snake_case
Python class names use PascalCase
Python functions/methods and local variables use snake_case; variables starting with a number get k_ prefix (e.g., k_99th_percentile)
Global variables use G_ prefixed UPPER_SNAKE_CASE (e.g., G_MY_GLOBAL)
Constants use UPPER_SNAKE_CASE in Python
Avoid shadowing variables from outer scopes in Python
Initialize all externally visible members of a Python class in init
Prefer docstrings for interfaces used outside a file; comments for local code
Use Google-style docstrings for classes and functions (Sphinx-parsable)
Document attributes/variables inline with short docstrings
Avoid reflection when simple alternatives exist (e.g., prefer explicit parameters over dict(**locals()))
In try/except, catch the narrowest exceptions possible
For duck-typing with try/except, keep try body minimal and put logic in else

Files:

  • tests/unittest/llmapi/test_llm_kv_cache_events.py
**/*.{cpp,cxx,cc,cu,h,hpp,hxx,hh,cuh,py}

📄 CodeRabbit Inference Engine (CODING_GUIDELINES.md)

Prepend NVIDIA copyright header (current year) to all source files

Files:

  • tests/unittest/llmapi/test_llm_kv_cache_events.py
🔇 Additional comments (1)
tests/unittest/llmapi/test_llm_kv_cache_events.py (1)

164-175: Good move away from brittle event_id == 1; accumulating stored blocks is robust

Replacing the hard-coded equality with event_id > 0 for "stored" events and summing block counts improves resilience across implementations.

@pcastonguay pcastonguay changed the title [nvbugs 5444937, 5451407][chore] Fixing KV events tests [nvbugs 5444937/5451407][chore] Fixing KV events tests Aug 18, 2025
@tensorrt-cicd
Copy link
Collaborator

PR_Github #15649 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #15629 [ run ] completed with state ABORTED

Signed-off-by: Patrice Castonguay <[email protected]>
@pcastonguay pcastonguay changed the title [nvbugs 5444937/5451407][chore] Fixing KV events tests [https://nvbugs/5444937][chore] Fixing KV events tests Aug 18, 2025
@pcastonguay
Copy link
Collaborator Author

/bot run --disable-fail-fast

@pcastonguay pcastonguay requested a review from Tabrizian August 18, 2025 17:57
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

♻️ Duplicate comments (1)
tests/unittest/llmapi/test_llm_kv_cache_events.py (1)

176-182: Guard is only partial; prefer get() and avoid pop(0) O(n) pattern

You added a None guard, but still assert the key and use direct indexing. Also, popping from the head in a loop is O(n) and unnecessary here.

Apply:

-        while events:
-            event = events.pop(0)
-            if not event:
-                continue
-            assert "attention_dp_rank" in event
-            if event["attention_dp_rank"] == attention_dp_rank:
+        for event in events:
+            if not event:
+                continue
+            if event.get("attention_dp_rank") != attention_dp_rank:
+                continue
🧹 Nitpick comments (3)
tests/unittest/llmapi/test_llm_kv_cache_events.py (3)

169-175: Minor: iterate instead of popping for clarity and to avoid O(n^2) behavior

Same nit as above for the non-attention branch.

-        while events:
-            event = events.pop(0)
-            if event:
-                assert event["data"]["type"] == "stored"
-                assert event["event_id"] > 0
-                total_stored_blocks += len(event["data"]["blocks"])
+        for event in events:
+            if not event:
+                continue
+            assert event["data"]["type"] == "stored"
+            assert event["event_id"] > 0
+            total_stored_blocks += len(event["data"]["blocks"])

189-189: Avoid hard-coded “5” block count; derive from first batch to reduce flakiness

Hardcoding 5 ties the test to internal block sizing. Derive the expected count from the first batch, then assert subsequent batches match.

Apply:

-    assert total_stored_blocks == 5  # Should have 5 blocks in total
+    expected_total_stored_blocks = total_stored_blocks
-    assert total_stored_blocks == 5  # Should have 5 blocks in total
+    assert total_stored_blocks == expected_total_stored_blocks
-    assert total_stored_blocks == 5  # Should have 5 blocks in total
+    assert total_stored_blocks == expected_total_stored_blocks

Additionally, initialize the variable at the top of check_events:

# inside check_events(...) near the top
expected_total_stored_blocks = None

Also applies to: 210-210, 232-232


203-211: Add sanity check: stored events should have event_id > 0

You relaxed this check earlier; keep it consistent in later batches too.

Apply:

         elif event["data"]["type"] == "stored":
+            assert event["event_id"] > 0
             total_stored_blocks += len(event["data"]["blocks"])

Apply the same in the third batch loop:

         elif event["data"]["type"] == "stored":
+            assert event["event_id"] > 0
             total_stored_blocks += len(event["data"]["blocks"])

Also applies to: 226-233

📜 Review details

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

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9c67018 and a98048d.

📒 Files selected for processing (1)
  • tests/unittest/llmapi/test_llm_kv_cache_events.py (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
**/*.py

📄 CodeRabbit Inference Engine (CODING_GUIDELINES.md)

**/*.py: Python code must target Python 3.8+
Python indentation: 4 spaces, no tabs
Maintain module namespace in imports (from package.subpackage import foo; then use foo.SomeClass())
Python file names use snake_case
Python class names use PascalCase
Python functions/methods and local variables use snake_case; variables starting with a number get k_ prefix (e.g., k_99th_percentile)
Global variables use G_ prefixed UPPER_SNAKE_CASE (e.g., G_MY_GLOBAL)
Constants use UPPER_SNAKE_CASE in Python
Avoid shadowing variables from outer scopes in Python
Initialize all externally visible members of a Python class in init
Prefer docstrings for interfaces used outside a file; comments for local code
Use Google-style docstrings for classes and functions (Sphinx-parsable)
Document attributes/variables inline with short docstrings
Avoid reflection when simple alternatives exist (e.g., prefer explicit parameters over dict(**locals()))
In try/except, catch the narrowest exceptions possible
For duck-typing with try/except, keep try body minimal and put logic in else

Files:

  • tests/unittest/llmapi/test_llm_kv_cache_events.py
**/*.{cpp,cxx,cc,cu,h,hpp,hxx,hh,cuh,py}

📄 CodeRabbit Inference Engine (CODING_GUIDELINES.md)

Prepend NVIDIA copyright header (current year) to all source files

Files:

  • tests/unittest/llmapi/test_llm_kv_cache_events.py
🧬 Code Graph Analysis (1)
tests/unittest/llmapi/test_llm_kv_cache_events.py (3)
tensorrt_llm/llmapi/llm.py (1)
  • get_kv_cache_events (471-490)
tensorrt_llm/serve/openai_server.py (1)
  • get_kv_cache_events (242-250)
tensorrt_llm/llmapi/utils.py (2)
  • get (354-367)
  • get (420-437)
⏰ 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)
tests/unittest/llmapi/test_llm_kv_cache_events.py (2)

164-175: Good move: relax event_id check and aggregate stored blocks

Switching to event_id > 0 and summing stored blocks makes the test less brittle than pinning to a specific id. Looks correct for non-attention DP.


173-174: Fix remaining brittle event_id assertion in executor bindings test

One instance of assert events[0].event_id == 1 still exists. Update it to a non‐strict check:

  • File: tests/unittest/bindings/test_executor_bindings.py, line 2023
  • Change:
  • assert events[0].event_id == 1
  • assert events[0].event_id > 0




> Likely an incorrect or invalid review comment.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

@tensorrt-cicd
Copy link
Collaborator

PR_Github #15651 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #15649 [ run ] completed with state ABORTED

@tensorrt-cicd
Copy link
Collaborator

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

@pcastonguay
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #15787 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

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

@pcastonguay pcastonguay merged commit e07fcc3 into NVIDIA:main Aug 19, 2025
5 of 6 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