Skip to content

[None][chore] AutoDeploy: Added Qwen3.5 accuracy test for NVFP4#13014

Merged
taylor-yb-lee merged 4 commits intoNVIDIA:mainfrom
nv-auto-deploy:taylor/qwen3.5_nvfp4_acctest
Apr 14, 2026
Merged

[None][chore] AutoDeploy: Added Qwen3.5 accuracy test for NVFP4#13014
taylor-yb-lee merged 4 commits intoNVIDIA:mainfrom
nv-auto-deploy:taylor/qwen3.5_nvfp4_acctest

Conversation

@taylor-yb-lee
Copy link
Copy Markdown
Collaborator

@taylor-yb-lee taylor-yb-lee commented Apr 13, 2026

Summary by CodeRabbit

  • New Features

    • Added support for NVFP4 quantization variant of the Qwen3.5-397B model.
  • Tests

    • Expanded test coverage for the new NVFP4 model variant.
    • Enhanced evaluation configuration with improved chat template and few-shot learning support.

Description

Added Qwen3.5 NVFP4 accuracy test for AutoDeploy
Measured score :
MMLU: 85
GSM8K:
image

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

  • 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

To see a list of available CI bot commands, please comment /bot help.

Signed-off-by: Taylor Yeonbok Lee <249374542+taylor-yb-lee@users.noreply.github.com>
Signed-off-by: Taylor Yeonbok Lee <249374542+taylor-yb-lee@users.noreply.github.com>
Signed-off-by: Taylor Yeonbok Lee <249374542+taylor-yb-lee@users.noreply.github.com>
@taylor-yb-lee taylor-yb-lee force-pushed the taylor/qwen3.5_nvfp4_acctest branch from a977fea to 484e3bb Compare April 13, 2026 20:41
@taylor-yb-lee taylor-yb-lee marked this pull request as ready for review April 13, 2026 23:28
@taylor-yb-lee taylor-yb-lee requested review from a team as code owners April 13, 2026 23:28
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 13, 2026

📝 Walkthrough

Walkthrough

The PR updates test infrastructure and model registry configurations for a new NVFP4 quantized variant of the Qwen3.5-397B model. It introduces a new test case, adds model-specific evaluation configuration, updates model path mappings, and disables a transform setting in the model registry configuration.

Changes

Cohort / File(s) Summary
Model Registry Configuration
examples/auto_deploy/model_registry/configs/qwen3.5_moe_400b.yaml
Disabled the initialize_mrope_delta_cache transform with updated inline comment clarifying that AutoModelForCausalLM does not consume this cache.
Test Infrastructure Updates
tests/integration/defs/accuracy/test_llm_api_autodeploy.py
Extended TestQwen3_5_397B_MoE class with new NVFP4 model constant, increased EXTRA_EVALUATOR_KWARGS configuration, added GSM8K_MAX_OUTPUT_LEN constant, modified test_bf16 signature to accept mocker parameter, and introduced new test_nvfp4 test method that runs NVFP4 model evaluation with quantization configuration and patched output limits.
Model Path Mapping
tests/test_common/llm_data.py
Added mapping entry for the new nvidia/Qwen3.5-397B-A17B-NVFP4 model variant to its local subdirectory.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description lacks critical sections required by the template: 'Description' section is incomplete (only states objective without explaining the issue/solution), and 'Test Coverage' section is empty despite substantive test changes. Fill in the Description section explaining what was changed and why (NVFP4 support, GSM8K max output length config), and explicitly list the new test_nvfp4 function added to TestQwen3_5_397B_MoE as test coverage.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: adding a Qwen3.5 NVFP4 accuracy test for AutoDeploy, matching the changeset's primary objective.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
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/test_common/llm_data.py (1)

1-1: ⚠️ Potential issue | 🟡 Minor

Update the copyright year on this modified file.

This file is being edited in 2026, but the header still ends at 2025.

As per coding guidelines, "Add NVIDIA copyright header on ALL new files and update year on modified files".

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@tests/test_common/llm_data.py` at line 1, Update the copyright header SPDX
line at the top of the file (the SPDX-FileCopyrightText comment) to include 2026
as the end year instead of 2025 so the header reflects the current modification
year; locate the SPDX-FileCopyrightText line in tests/test_common/llm_data.py
and change the year range to 2022-2026.
🧹 Nitpick comments (1)
tests/integration/defs/accuracy/test_llm_api_autodeploy.py (1)

812-816: Prefer generating these evaluator kwargs per test invocation.

EXTRA_EVALUATOR_KWARGS is a shared nested dict on the class. If any evaluator mutates it, state can leak between the BF16 and NVFP4 runs. A tiny helper returning a fresh dict avoids that coupling.

♻️ Suggested change
-    EXTRA_EVALUATOR_KWARGS = dict(
-        apply_chat_template=True,
-        fewshot_as_multiturn=True,
-        chat_template_kwargs=dict(enable_thinking=False),
-    )
+    `@staticmethod`
+    def _extra_evaluator_kwargs():
+        return {
+            "apply_chat_template": True,
+            "fewshot_as_multiturn": True,
+            "chat_template_kwargs": {"enable_thinking": False},
+        }

Then update both task.evaluate(..., extra_evaluator_kwargs=...) call sites to pass self._extra_evaluator_kwargs().

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@tests/integration/defs/accuracy/test_llm_api_autodeploy.py` around lines 812
- 816, EXTRA_EVALUATOR_KWARGS is a shared mutable dict that can leak state
between tests; replace it with a small helper method (e.g., def
_extra_evaluator_kwargs(self): ...) that returns a fresh dict with
apply_chat_template=True, fewshot_as_multiturn=True, and
chat_template_kwargs={'enable_thinking': False}, and update both
task.evaluate(..., extra_evaluator_kwargs=...) call sites to pass
self._extra_evaluator_kwargs() instead of the module/class-level
EXTRA_EVALUATOR_KWARGS.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@tests/integration/defs/accuracy/test_llm_api_autodeploy.py`:
- Around line 865-866: In test_nvfp4, the registry config is fetched for the
base model name; update the call to _get_registry_yaml_extra to use the NVFP4
variant by replacing self.MODEL_NAME with self.MODEL_NAME_NVFP4 so the test
loads the correct registry YAML for the NVFP4 model (look for the
_get_registry_yaml_extra(...) invocation in test_nvfp4 and change the argument
to self.MODEL_NAME_NVFP4).

---

Outside diff comments:
In `@tests/test_common/llm_data.py`:
- Line 1: Update the copyright header SPDX line at the top of the file (the
SPDX-FileCopyrightText comment) to include 2026 as the end year instead of 2025
so the header reflects the current modification year; locate the
SPDX-FileCopyrightText line in tests/test_common/llm_data.py and change the year
range to 2022-2026.

---

Nitpick comments:
In `@tests/integration/defs/accuracy/test_llm_api_autodeploy.py`:
- Around line 812-816: EXTRA_EVALUATOR_KWARGS is a shared mutable dict that can
leak state between tests; replace it with a small helper method (e.g., def
_extra_evaluator_kwargs(self): ...) that returns a fresh dict with
apply_chat_template=True, fewshot_as_multiturn=True, and
chat_template_kwargs={'enable_thinking': False}, and update both
task.evaluate(..., extra_evaluator_kwargs=...) call sites to pass
self._extra_evaluator_kwargs() instead of the module/class-level
EXTRA_EVALUATOR_KWARGS.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 8db2a9df-4ed9-4c2f-a742-c0a515b63bea

📥 Commits

Reviewing files that changed from the base of the PR and between a2557ad and 484e3bb.

📒 Files selected for processing (3)
  • examples/auto_deploy/model_registry/configs/qwen3.5_moe_400b.yaml
  • tests/integration/defs/accuracy/test_llm_api_autodeploy.py
  • tests/test_common/llm_data.py

Comment thread tests/integration/defs/accuracy/test_llm_api_autodeploy.py
@nvchenghaoz
Copy link
Copy Markdown
Collaborator

@taylor-yb-lee If this model needs to be in the CI, you might want to add this test to tests/integration/test_lists/test-db/, file a MR to add the model to "llm-models".

Please also update the tests/integration/defs/accuracy/references/mmlu.yaml and tests/integration/defs/accuracy/references/gsm8k.yaml

Signed-off-by: Taylor Yeonbok Lee <249374542+taylor-yb-lee@users.noreply.github.com>
@taylor-yb-lee
Copy link
Copy Markdown
Collaborator Author

/bot skip "added only post-merge tests"

@github-actions
Copy link
Copy Markdown

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.

Details

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) --high-priority]

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.

--high-priority (OPTIONAL) : Run the pipeline with high priority. This option is restricted to authorized users only and will route the job to a high-priority queue.

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.

@taylor-yb-lee taylor-yb-lee enabled auto-merge (squash) April 14, 2026 01:17
@taylor-yb-lee
Copy link
Copy Markdown
Collaborator Author

/bot skip --comment "added only post-merge tests"

@tensorrt-cicd
Copy link
Copy Markdown
Collaborator

PR_Github #43181 [ skip ] triggered by Bot. Commit: df42600 Link to invocation

@tensorrt-cicd
Copy link
Copy Markdown
Collaborator

PR_Github #43181 [ skip ] completed with state SUCCESS. Commit: df42600
Skipping testing for commit df42600

Link to invocation

@taylor-yb-lee taylor-yb-lee merged commit dcb4a71 into NVIDIA:main Apr 14, 2026
5 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