Skip to content

Conversation

chuangz0
Copy link
Collaborator

@chuangz0 chuangz0 commented Jul 18, 2025

…ot_limit

Summary by CodeRabbit

  • Tests
    • Updated a test to align its configuration and environment settings with other similar tests, ensuring consistency in test setups.

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.

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.

@chuangz0 chuangz0 requested a review from Tabrizian July 18, 2025 02:28
Copy link
Contributor

coderabbitai bot commented Jul 18, 2025

Walkthrough

The test test_disaggregated_spec_dec_batch_slot_limit in the integration suite was updated to include cache_transceiver_configs in its worker arguments and to use the "UCX_TLS": "^ib" environment variable for the MPI pool executor, aligning it with other similar tests in the file.

Changes

File(s) Change Summary
tests/integration/defs/disaggregated/test_disaggregated_single_gpu.py Modified a test to add cache_transceiver_configs to worker args and updated the MPI pool executor environment variable.

Suggested reviewers

  • pcastonguay
  • mikeiovine

Poem

In the warren of tests, a config hops in,
With transceivers aligned, the batch slots begin.
UCX whispers secrets, MPI takes a bow,
The single GPU smiles, all is in sync now.
🐇✨


📜 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 920c219 and 94036b6.

📒 Files selected for processing (1)
  • tests/integration/defs/disaggregated/test_disaggregated_single_gpu.py (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • tests/integration/defs/disaggregated/test_disaggregated_single_gpu.py
✨ 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.

@chuangz0
Copy link
Collaborator Author

/bot run --stage-list "H100_PCIe-PyTorch-1"

@chuangz0 chuangz0 force-pushed the fix_disagg_spec_dec_batch_slot branch from 920c219 to 94036b6 Compare July 18, 2025 02:30
@tensorrt-cicd
Copy link
Collaborator

PR_Github #12261 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

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

@chuangz0 chuangz0 requested a review from chzblych July 18, 2025 04:54
@chuangz0
Copy link
Collaborator Author

/bot skip --comment "the failed stage has passed"

@chuangz0 chuangz0 enabled auto-merge (squash) July 18, 2025 04:55
@tensorrt-cicd
Copy link
Collaborator

PR_Github #12276 [ skip ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #12276 [ skip ] completed with state SUCCESS
Skipping testing for commit 94036b6

@chuangz0 chuangz0 merged commit c0e4165 into NVIDIA:main Jul 18, 2025
3 checks passed
reasonsolo pushed a commit to reasonsolo/TensorRT-LLM that referenced this pull request Jul 21, 2025
timlee0212 pushed a commit to timlee0212/TensorRT-LLM that referenced this pull request Jul 21, 2025
NVShreyas pushed a commit to NVShreyas/TensorRT-LLM that referenced this pull request Jul 28, 2025
Signed-off-by: Chuang Zhu <[email protected]>
Signed-off-by: Shreyas Misra <[email protected]>
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