Skip to content

Conversation

@ixlmar
Copy link
Collaborator

@ixlmar ixlmar commented Nov 19, 2025

Description

This PR makes the test pass when FlashInfer.sampling is enabled (cf. #9270).

Test Coverage

n/a

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

  • Update tava architecture diagram if there is a significant design change in PR.

  • 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.

Summary by CodeRabbit

Release Notes

This release contains no user-facing changes. Internal test configurations have been updated to support ongoing development and quality assurance efforts.

@ixlmar
Copy link
Collaborator Author

ixlmar commented Nov 19, 2025

/bot run

@ixlmar ixlmar requested a review from Funatiq November 19, 2025 13:40
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 19, 2025

📝 Walkthrough

Walkthrough

A temperature parameter set to 0.0 was added to a chat.completions.create API call within a test method, modifying the request configuration without altering test logic or public APIs.

Changes

Cohort / File(s) Change Summary
Test API Configuration
tests/unittest/llmapi/apps/_test_openai_chat_guided_decoding.py
Added temperature=0.0 parameter to chat.completions.create call in test_openai_compatible_json_schema test method

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • Isolated test file modification with single parameter addition
  • No logic changes or public API modifications

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: adding greedy decoding (temperature=0.0) to a test. It is directly related to the changeset and follows the repository template format.
Description check ✅ Passed The description provides the context (FlashInfer.sampling enablement) and references a related issue, but lacks specific technical details about how the fix works or why temperature=0.0 implements greedy decoding.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent 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 46dd988 and 15f1eec.

📒 Files selected for processing (1)
  • tests/unittest/llmapi/apps/_test_openai_chat_guided_decoding.py (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). (1)
  • GitHub Check: Pre-commit Check
🔇 Additional comments (1)
tests/unittest/llmapi/apps/_test_openai_chat_guided_decoding.py (1)

139-139: Now let me search for context about why the fix is applied only to one test:

Let me search for more specific information about whether both test variants should have the temperature fix:

Based on my verification, I now have a clear picture of why only test_openai_compatible_json_schema needs the temperature fix:

The two tests use fundamentally different OpenAI API features:

  • test_json_schema: Uses "type": "json" (older JSON mode) — does not enforce strict schema adherence, uses best-effort validation
  • test_openai_compatible_json_schema: Uses "type": "json_schema" (Structured Outputs) — enforces strict schema conformance using constrained token-level decoding

Structured Outputs uses grammar-based constrained sampling where after every token, the inference engine determines which tokens are valid based on the schema grammar and masks invalid tokens by setting their probability to 0. This token-level constraint is sensitive to non-deterministic sampling behavior from FlashInfer.

JSON mode improves model reliability for generating valid JSON outputs, but does not guarantee that the model's response will conform to a particular schema, making it less sensitive to sampling variability.

The temperature=0.0 fix in test_openai_compatible_json_schema is therefore intentional and appropriate to that specific test variant. There is no evidence that test_json_schema requires the same fix.

Apply temperature=0.0 only to the json_schema variant, as currently implemented. No changes needed.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


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.

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25053 [ run ] triggered by Bot. Commit: 15f1eec

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25053 [ run ] completed with state SUCCESS. Commit: 15f1eec
/LLM/main/L0_MergeRequest_PR pipeline #18934 completed with status: 'FAILURE'

@ixlmar
Copy link
Collaborator Author

ixlmar commented Nov 19, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #25069 [ run ] triggered by Bot. Commit: 15f1eec

@tensorrt-cicd
Copy link
Collaborator

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

@ixlmar ixlmar merged commit a39e8c5 into NVIDIA:main Nov 20, 2025
8 of 9 checks passed
@ixlmar ixlmar deleted the fix/json-schema-test branch November 20, 2025 07:32
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