[None][fix] fix CUDA graph config for test_llm_api_pytorch.py.

[yuxianq]

Summary by CodeRabbit

• Refactor

  • Replaced the boolean flag for enabling CUDA Graphs with a configuration object during model initialization. Passing a config enables it; passing None disables it. This updates the public API.

• Tests

  • Updated integration tests to use the new CUDA Graph configuration pattern without changing expectations or outcomes.

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.

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

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

Replaced use_cuda_graph boolean parameters with cuda_graph_config objects in LLM initialization within tests/integration/defs/accuracy/test_llm_api_pytorch.py. Calls now pass cuda_graph_config=CudaGraphConfig() when enabled, else None. No assertions changed. Public API updated: LLM.init now accepts Optional[CudaGraphConfig] instead of use_cuda_graph: bool.

Changes

Cohort / File(s)	Summary
Tests: CUDA graph config adoption tests/integration/defs/accuracy/test_llm_api_pytorch.py	Updated LLM constructor calls to use cuda_graph_config=CudaGraphConfig() or None based on cuda_graph flag across test_fp8, test_fp8_chunked_prefill, and test_fp4_chunked_prefill in Maverick/Scout classes. Reflected API change from use_cuda_graph -> cuda_graph_config.

Sequence Diagram(s)

sequenceDiagram
    participant Test as Test (PyTorch accuracy)
    participant LLM as LLM.__init__
    participant CG as CudaGraphConfig

    Test->>LLM: __init__(..., cuda_graph_config = CudaGraphConfig() or None)
    alt cuda_graph enabled
        LLM->>CG: Use default CUDA Graph settings
        LLM-->>Test: LLM instance with CUDA Graph configured
    else disabled
        LLM-->>Test: LLM instance without CUDA Graph
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• tests: add TestNemotronH cuda graph tests #6390: Similar transition in tests to pass cuda_graph_config to LLM constructors, replacing use_cuda_graph.
• [https://nvbugs/5442608][fix] Update CUDA graph config for get_model_yaml_config. #6693: Broad refactor unifying CUDA graph-related flags into cuda_graph_config across the codebase.

Suggested reviewers

• nv-guomingz
• ruodil
• StanleySun639

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a32a2e4 and 9a03824.

📒 Files selected for processing (1)

• tests/integration/defs/accuracy/test_llm_api_pytorch.py (4 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/integration/defs/accuracy/test_llm_api_pytorch.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/integration/defs/accuracy/test_llm_api_pytorch.py

🔇 Additional comments (4)

tests/integration/defs/accuracy/test_llm_api_pytorch.py (4)

506-507: Correct: migrated to CudaGraphConfig in LLM init

Switching to cuda_graph_config=CudaGraphConfig() if cuda_graph else None aligns with the new LLM API and preserves previous behavior. LGTM.

---

530-531: Correct: CUDA graph configuration passed via CudaGraphConfig

This change reflects the updated API and is consistent with other call sites. LGTM.

---

651-652: Correct: updated to use CudaGraphConfig for FP8 chunked prefill

The wiring is correct and consistent with the rest of the file. LGTM.

---

674-675: Correct: updated to use CudaGraphConfig for FP4 chunked prefill

Matches the new API semantics. LGTM.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[yuxianq]

/bot run

[tensorrt-cicd]

PR_Github #14960 [ run ] triggered by Bot

[QiJune]

LGTM

[crazydemo]

LGTM

[tensorrt-cicd]

PR_Github #14960 [ run ] completed with state SUCCESS
/LLM/release-1.0/L0_MergeRequest_PR pipeline #65 completed with status: 'SUCCESS'