Skip to content

Conversation

yizhang-nv
Copy link
Member

@yizhang-nv yizhang-nv commented Jul 17, 2025

PR title

Please write the PR title by following template:

[JIRA ticket link/nvbug link/github issue link][fix/feat/doc/infra/...] <summary of this PR>

For example, assume I have a PR hope to support a new feature about cache manager of Jira TRTLLM-1000 ticket, it would be like

[TRTLLM-1000][feat] Support a new feature about cache manager

Description

Please explain the issue and the solution in short.

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.

run [--disable-fail-fast --skip-test --stage-list "A10-1, xxx" --gpu-type "A30, H100_PCIe" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-[Post-Merge]-1, xxx"]

Launch build/test pipelines. All previously running jobs will be killed.

--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-1, xxx" (OPTIONAL) : Only run the specified test stages. Examples: "A10-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.

--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. Will also run 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-[Post-Merge]-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-[Post-Merge]-1, xxx".

For guidance on mapping tests to stage names, see docs/source/reference/ci-overview.md.

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

  • Tests
    • Adjusted GPU memory usage settings in multi-GPU tests for improved accuracy.
    • Updated internal test checks to ensure correct backend verification.
    • Removed skip entries for specific latency and throughput tests related to a known bug.

Copy link
Contributor

coderabbitai bot commented Jul 17, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The test method test_nvfp4_multi_gpus in the TestDeepSeekR1 class was updated by adjusting the free_gpu_memory_fraction parameter from 0.85 to 0.80 for the key-value cache configuration and correcting the assertion to check the MOE backend via llm.args.moe_config.backend instead of llm.args.moe_backend. Additionally, two skip entries related to this test were removed from the waive list. No public interfaces were changed.

Changes

File(s) Change Summary
tests/integration/defs/accuracy/test_llm_api_pytorch.py Adjusted free_gpu_memory_fraction from 0.85 to 0.80 and fixed MOE backend assertion attribute
tests/integration/test_lists/waives.txt Removed two skip entries for test_nvfp4_multi_gpus referencing bug https://nvbugs/5397036

Poem

In the warren of tests, a fraction did shift,
From eighty-five to eighty, a subtle, careful lift.
The backend path now rightly aligned,
No more assertion errors to find!
🐇 With every tweak and little fix,
Our code hops forward—swift and slick!


📜 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 8248a17 and 0db7aef.

📒 Files selected for processing (2)
  • tests/integration/defs/accuracy/test_llm_api_pytorch.py (2 hunks)
  • tests/integration/test_lists/waives.txt (0 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

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 anywhere in the PR title to generate the title automatically.

Documentation and Community

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

@yizhang-nv
Copy link
Member Author

/bot run --stage-list "GB200-8_GPUs-2_Nodes-PyTorch-Post-Merge-1,GB200-8_GPUs-2_Nodes-PyTorch-Post-Merge-2,GB200-8_GPUs-2_Nodes-PyTorch-Post-Merge-3,GB200-8_GPUs-2_Nodes-PyTorch-Post-Merge-4"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12161 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12161 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9032 (Partly Tested) completed with status: 'SUCCESS'

@yizhang-nv yizhang-nv marked this pull request as ready for review July 17, 2025 09:06
@yizhang-nv
Copy link
Member Author

/bot skip --comment "All related tests are passed"

@yizhang-nv
Copy link
Member Author

/bot skip --comment "All related tests are passed"

@yizhang-nv yizhang-nv enabled auto-merge (squash) July 17, 2025 09:24
@tensorrt-cicd
Copy link
Collaborator

PR_Github #12190 [ skip ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12190 [ skip ] completed with state SUCCESS
Skipping testing for commit 4f79e81

@yizhang-nv
Copy link
Member Author

/bot skip --comment "All related tests are passed"

@litaotju litaotju disabled auto-merge July 17, 2025 10:24
Signed-off-by: Yi Zhang <[email protected]>
Signed-off-by: Yi Zhang <[email protected]>
@litaotju litaotju merged commit a718486 into NVIDIA:main Jul 17, 2025
2 checks passed
@tensorrt-cicd
Copy link
Collaborator

PR_Github #12197 [ ] completed with state FAILURE
Not allowed on merged PR

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.

5 participants