KEMBAR78
[TRTLLM-6643][feat] Add DeepSeek-v3-0324 e2e torch test by aalanwyr · Pull Request #7413 · NVIDIA/TensorRT-LLM · GitHub
Skip to content

Conversation

@aalanwyr
Copy link
Collaborator

@aalanwyr aalanwyr commented Sep 1, 2025

Summary by CodeRabbit

  • Tests
    • Expanded end-to-end coverage to include new DeepSeek model variants, including multi-node and 8‑GPU scenarios.
    • Updated resource expectations and skip rules to reflect hardware constraints for high-memory configurations.
    • Added corresponding entries to QA test lists to ensure these scenarios are exercised in CI.
    • No functional changes to the product; improvements focus on reliability and validation.

Description

Add DeepSeek-v3-0324 into nim test scope
Add two e2e test cases for DeepSeek-v3-0324
Single-nodes-multi-gpus: test_e2e.py::test_ptp_quickstart_advanced_8gpus[DeepSeek-V3-671B-FP8-DeepSeek-V3-0324]
Verified this test on 8XH20

GPU Config Peak Mem usage
H20 8X(141GB) 137 GB

Multi-nodes-multi-gpus: test_e2e.py::test_ptp_quickstart_advanced_deepseek_multi_nodes[DeepSeek-V3-0324]

Verified on cluster:
https://prod.blsm.nvidia.com/swqa-tensorrt-qa-test/blue/organizations/jenkins/DEBUG_LLM_FUNCTION_CLUSTER_TEST/detail/DEBUG_LLM_FUNCTION_CLUSTER_TEST/147/pipeline/

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.

Signed-off-by: Yaran Wu <28771492+aalanwyr@users.noreply.github.com>
Signed-off-by: Yaran Wu <28771492+aalanwyr@users.noreply.github.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 1, 2025

📝 Walkthrough

Walkthrough

Adds DeepSeek-V3-0324 to multiple integration test parameterizations and expected-memory mapping, introduces an 8-GPU relaxed-acceptance entry using DeepSeek-V3-671B-FP8 with skip markers, and appends corresponding test identifiers to multi-node and NIM QA test lists. No production logic or public API changes.

Changes

Cohort / File(s) Summary
Integration tests updates
tests/integration/defs/test_e2e.py
Add DeepSeek-V3-0324 to model_path matrices; add DeepSeek-V3-671B-FP8 (using DeepSeek-V3-0324 path) to 8-GPU relaxed test with skip markers; extend expected-memory map with 50.0 for DeepSeek-V3-0324.
QA test lists updates
tests/integration/test_lists/qa/llm_function_multinode.txt, tests/integration/test_lists/qa/llm_function_nim.txt
Append new test entries referencing the added DeepSeek variants for multi-node and NIM 8-GPU runs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

  • crazydemo
  • xinhe-nv
  • litaotju
✨ 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 or @coderabbit 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.

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

📜 Review details

Configuration used: Path: .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 b0558c7 and 3a75561.

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

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

**/*.{cpp,cc,cxx,cu,h,hpp,hh,hxx,cuh,py}: Use spaces only; no tabs; indent with 4 spaces
Prepend NVIDIA copyright header (current year) to all source files (.cpp, .h, .cu, .py, etc.)

Files:

  • tests/integration/defs/test_e2e.py
**/*.py

📄 CodeRabbit inference engine (CODING_GUIDELINES.md)

**/*.py: Python code must target Python 3.8+
Indent Python with 4 spaces; no tabs
Preserve module namespaces when importing: from package.subpackage import foo; then call foo.SomeClass() instead of importing the class directly
Python naming: files snake_case; classes PascalCase; functions/methods snake_case; locals snake_case (prefix k_ when starting with a number); globals UPPER_SNAKE_CASE with G_ prefix; constants UPPER_SNAKE_CASE
Avoid shadowing outer-scope variables; initialize all externally visible members in init
Prefer docstrings for interfaces used outside a file; limit comments to function-internal or file-local interfaces
Use Google-style docstrings for classes and functions; document attributes/variables inline so Sphinx can render them
Avoid reflection when simpler alternatives exist; prefer explicit parameters and return dicts over locals()/dynamic tricks
In try/except, catch the narrowest exceptions possible; keep try bodies minimal and use else for the main logic when doing duck-typing checks

Files:

  • tests/integration/defs/test_e2e.py
🧠 Learnings (2)
📚 Learning: 2025-07-28T17:06:08.621Z
Learnt from: moraxu
PR: NVIDIA/TensorRT-LLM#6303
File: tests/integration/test_lists/qa/examples_test_list.txt:494-494
Timestamp: 2025-07-28T17:06:08.621Z
Learning: In TensorRT-LLM testing, it's common to have both CLI flow tests (test_cli_flow.py) and PyTorch API tests (test_llm_api_pytorch.py) for the same model. These serve different purposes: CLI flow tests validate the traditional command-line workflow, while PyTorch API tests validate the newer LLM API backend. Both are legitimate and should coexist.

Applied to files:

  • tests/integration/test_lists/qa/llm_function_nim.txt
  • tests/integration/defs/test_e2e.py
📚 Learning: 2025-08-29T14:07:45.863Z
Learnt from: EmmaQiaoCh
PR: NVIDIA/TensorRT-LLM#7370
File: tests/unittest/trt/model_api/test_model_quantization.py:24-27
Timestamp: 2025-08-29T14:07:45.863Z
Learning: In TensorRT-LLM's CI infrastructure, pytest skip markers (pytest.mark.skip) are properly honored even when test files have __main__ blocks that call test functions directly. The testing system correctly skips tests without requiring modifications to the __main__ block execution pattern.

Applied to files:

  • tests/integration/defs/test_e2e.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 (3)
tests/integration/test_lists/qa/llm_function_multinode.txt (1)

9-9: DeepSeek-V3-0324 multinode entry added — looks good

Entry matches the new param in test_e2e; no issues spotted.

Confirm you intend to keep both entries (DeepSeek-V3 and DeepSeek-V3-0324) enabled to run side-by-side, not replace one with the other.

tests/integration/test_lists/qa/llm_function_nim.txt (1)

2-2: NIM list entry aligns with new 8-GPU param

The ID format mirrors the two-parameter parametrize; OK.

tests/integration/defs/test_e2e.py (1)

1913-1913: Added DeepSeek-V3-0324 to multinode test matrix — OK

Marker choice (skip_post_blackwell) is consistent with the existing DeepSeek-V3 entry.

@aalanwyr aalanwyr changed the title TRTLLM-6643 : [QA]DeepSeek-v3-0324 torch test [TRTLLM-6643][feat] add DeepSeek-v3-0324 e2e torch test Sep 1, 2025
@aalanwyr aalanwyr changed the title [TRTLLM-6643][feat] add DeepSeek-v3-0324 e2e torch test [TRTLLM-6643][feat] Add DeepSeek-v3-0324 e2e torch test Sep 1, 2025
Signed-off-by: Yaran Wu <28771492+aalanwyr@users.noreply.github.com>
Signed-off-by: Yaran Wu <28771492+aalanwyr@users.noreply.github.com>
Signed-off-by: Yaran Wu <28771492+aalanwyr@users.noreply.github.com>
@aalanwyr
Copy link
Collaborator Author

aalanwyr commented Sep 2, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17271 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

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

Signed-off-by: Yaran Wu <28771492+aalanwyr@users.noreply.github.com>
Signed-off-by: Yaran Wu <28771492+aalanwyr@users.noreply.github.com>
@aalanwyr
Copy link
Collaborator Author

aalanwyr commented Sep 2, 2025

/bot run

@tensorrt-cicd
Copy link
Collaborator

PR_Github #17302 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

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

@crazydemo crazydemo merged commit c3c9573 into NVIDIA:main Sep 2, 2025
7 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.

4 participants