Skip to content

Conversation

@VALLIS-NERIA
Copy link
Collaborator

@VALLIS-NERIA VALLIS-NERIA commented Oct 22, 2025

Summary by CodeRabbit

  • Tests
    • Updated test configuration and conditions for backend-specific testing scenarios.

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.

@VALLIS-NERIA VALLIS-NERIA requested a review from xinhe-nv October 22, 2025 11:34
@VALLIS-NERIA VALLIS-NERIA self-assigned this Oct 22, 2025
@VALLIS-NERIA VALLIS-NERIA requested a review from a team as a code owner October 22, 2025 11:34
@VALLIS-NERIA
Copy link
Collaborator Author

/bot run

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 22, 2025

📝 Walkthrough

Walkthrough

Test decorator in test_extra_llm_api_options changed from skip_pre_hopper to skip_no_hopper with an added contextual comment indicating backend specifics. Import alias updated accordingly.

Changes

Cohort / File(s) Summary
Test Decorator Update
tests/integration/defs/examples/serve/test_serve.py
Updated test_extra_llm_api_options test decorator from skip_pre_hopper to skip_no_hopper; added contextual comment regarding backend specifics; updated import alias to align with new skip condition

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (3 warnings)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
Title Check ⚠️ Warning The PR title follows the correct format with the NVBugs ID [https://nvbugs/5601203], type [fix], and summary text. However, based on the raw summary of changes, the actual code modifications involve replacing a test decorator from skip_pre_hopper to skip_no_hopper and adding a contextual comment in a test file. The title describing "Restrict fp8 blockscale moe case" does not accurately reflect these decorator and comment-related changes in the test file, making the title misleading about the actual content of the changeset. Update the PR title to accurately reflect the actual changes. For example, consider: "[https://nvbugs/5601203][fix] Update test decorator for extra llm api options test" or a title that better describes the purpose of changing the test condition. Ensure the title conveys what the code changes actually accomplish rather than using a title that suggests different functional changes.
Description Check ⚠️ Warning The PR description contains only the template structure with empty sections. The "Description" section, which should explain the issue and solution, contains only the template comment placeholder with no actual content. Similarly, the "Test Coverage" section that should list relevant tests is empty. While the PR Checklist box is marked as checked, the core required sections that communicate the purpose and context of the changes are entirely unfilled, leaving reviewers without essential information about what problem is being addressed or why. Fill in the required sections of the PR description. In the Description section, explain what the issue is and how the decorator change (skip_pre_hopper to skip_no_hopper) addresses it. In the Test Coverage section, specify which tests validate these changes and why the decorator modification is necessary. Provide sufficient context so reviewers understand the rationale and impact of restricting the fp8 blockscale MOE case as indicated in the NVBugs ticket.
✨ 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: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
tests/integration/defs/examples/serve/test_serve.py (1)

1-1: Add required NVIDIA Apache-2.0 copyright header.

The file is missing the required NVIDIA Apache-2.0 copyright header with the current year (2025) at the top. This is mandated by the coding guidelines for all Python source files.

As per coding guidelines

Add the copyright header at the top of the file:

+# SPDX-FileCopyrightText: Copyright (c) 2025 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-License-Identifier: Apache-2.0
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
 import os
 import time
📜 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 e86d6db and 93870b6.

📒 Files selected for processing (1)
  • tests/integration/defs/examples/serve/test_serve.py (2 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{h,hpp,hh,hxx,cpp,cxx,cc,cu,cuh,py}

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

Use only spaces, no tabs; indent with 4 spaces.

Files:

  • tests/integration/defs/examples/serve/test_serve.py
**/*.py

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

**/*.py: Python code must target Python 3.8+.
Indent Python code with 4 spaces; do not use tabs.
Maintain module namespace when importing; prefer 'from package.subpackage import foo' then 'foo.SomeClass()' instead of importing the class directly.
Python filenames should be snake_case (e.g., some_file.py).
Python classes use PascalCase names.
Functions and methods use snake_case names.
Local variables use snake_case; prefix 'k' for variables that start with a number (e.g., k_99th_percentile).
Global variables use upper SNAKE_CASE prefixed with 'G' (e.g., G_MY_GLOBAL).
Constants use upper SNAKE_CASE (e.g., MY_CONSTANT).
Avoid shadowing variables from an outer scope.
Initialize all externally visible members of a class in the constructor.
Prefer docstrings for interfaces that may be used outside a file; comments for in-function or file-local interfaces.
Use Google-style docstrings for classes and functions (Sphinx-parsable).
Document attributes and variables inline so they render under the class/function docstring.
Avoid reflection when a simpler, explicit approach suffices (e.g., avoid dict(**locals()) patterns).
In try/except, catch the most specific exceptions possible.
For duck-typing try/except, keep the try body minimal and use else for the main logic.

Files:

  • tests/integration/defs/examples/serve/test_serve.py
**/*.{cpp,cxx,cc,h,hpp,hh,hxx,cu,cuh,py}

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

Prepend the NVIDIA Apache-2.0 copyright header with current year to the top of all source files (e.g., .cpp, .h, .cu, .py).

Files:

  • tests/integration/defs/examples/serve/test_serve.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)
tests/integration/defs/examples/serve/test_serve.py (2)

96-132: Test implementation looks good.

The test correctly validates the Hopper-specific FP8 blockscale MoE configuration by:

  • Verifying required files exist
  • Launching the server with appropriate configuration
  • Validating server health before testing
  • Performing functional validation via OpenAI chat completion

The restriction to Hopper is appropriate given the CUTLASS backend constraint.


5-5: Decorator semantics verified—no issues found.

The skip_no_hopper decorator correctly skips tests when SM version is not 90 (Hopper). The change from skip_pre_hopper to skip_no_hopper is semantically appropriate for ensuring this test runs only on Hopper architecture, aligning with the CUTLASS FP8 blockscale constraint.

@tensorrt-cicd
Copy link
Collaborator

PR_Github #22179 [ run ] triggered by Bot. Commit: 93870b6

@VALLIS-NERIA VALLIS-NERIA changed the title [https://nvbugs/5601203] [fix]Restrict fp8 blocksacle moe case [https://nvbugs/5601203] [fix]Restrict fp8 blockscale moe case Oct 22, 2025
Signed-off-by: xiweny <[email protected]>
@VALLIS-NERIA
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #22180 [ run ] triggered by Bot. Commit: fc9bab7

@tensorrt-cicd
Copy link
Collaborator

PR_Github #22179 [ run ] completed with state ABORTED. Commit: 93870b6
LLM/release-1.1/L0_MergeRequest_PR #227 (Blue Ocean) completed with status: ABORTED

@tensorrt-cicd
Copy link
Collaborator

PR_Github #22180 [ run ] completed with state SUCCESS. Commit: fc9bab7
/LLM/release-1.1/L0_MergeRequest_PR pipeline #228 completed with status: 'FAILURE'

@VALLIS-NERIA
Copy link
Collaborator Author

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #22227 [ run ] triggered by Bot. Commit: fc9bab7

@tensorrt-cicd
Copy link
Collaborator

PR_Github #22227 [ run ] completed with state SUCCESS. Commit: fc9bab7
/LLM/release-1.1/L0_MergeRequest_PR pipeline #234 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