Skip to content

Conversation

yiqingy0
Copy link
Collaborator

@yiqingy0 yiqingy0 commented Jul 31, 2025

Summary by CodeRabbit

  • Refactor
    • Improved handling of merge request diff content by switching from inline arguments to file-based processing for better reliability.
    • Updated command-line interface to use a file input for diff content.
  • Bug Fixes
    • Enabled numerous tests previously disabled on Blackwell B200 and B200_PCIe platforms by removing skip entries.

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 [--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: Yiqing Yan <[email protected]>
Copy link
Contributor

coderabbitai bot commented Jul 31, 2025

📝 Walkthrough

Walkthrough

This change updates the handling of diff content in the Jenkins merge waive list process. Instead of passing the diff as a string argument to the Python script, the diff is now written to a temporary file and passed via a new --diff-file argument. The Python script is updated to read and process the diff from this file. Additionally, a large number of test skip entries related to Blackwell hardware on B200 and B200_PCIe platforms were removed from the integration test waives list.

Changes

Cohort / File(s) Change Summary
Jenkins Pipeline Script Update
jenkins/L0_MergeRequest.groovy
Modified the mergeWaiveList function to write diff content to a temporary file and invoke the Python script with a --diff-file argument instead of passing the diff string directly.
Python Script Argument and Function Update
jenkins/scripts/mergeWaiveList.py
Renamed function get_remove_lines_from_diff to get_remove_lines_from_diff_file and changed its signature to accept a filename. Updated command-line argument from --diff to --diff-file and adjusted logic to read and process the diff from a file.
Integration Test Waives Update
tests/integration/test_lists/waives.txt
Removed numerous skip entries for tests disabled on Blackwell hardware (B200 and B200_PCIe platforms), enabling many previously disabled tests for these platforms. No structural changes to the file were made.

Sequence Diagram(s)

sequenceDiagram
    participant JenkinsPipeline as Jenkins Pipeline (Groovy)
    participant TempFile as Temporary Diff File
    participant MergeScript as mergeWaiveList.py

    JenkinsPipeline->>TempFile: Write diff content to diff_content.txt
    JenkinsPipeline->>MergeScript: Call with --diff-file diff_content.txt
    MergeScript->>TempFile: Read diff content
    MergeScript->>MergeScript: Process removed lines from diff
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

Suggested reviewers

  • chzblych
  • niukuo
  • ZhanruiSunCh

📜 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 582e24d and 064350d.

📒 Files selected for processing (1)
  • jenkins/scripts/mergeWaiveList.py (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • jenkins/scripts/mergeWaiveList.py
✨ 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.
    • 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 generate unit tests to generate unit tests for 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 or @coderabbitai title 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.

Signed-off-by: Yiqing Yan <[email protected]>
@yiqingy0
Copy link
Collaborator Author

/bot run

Signed-off-by: Yiqing Yan <[email protected]>
@tensorrt-cicd
Copy link
Collaborator

PR_Github #13619 [ run ] triggered by Bot

@yiqingy0 yiqingy0 marked this pull request as ready for review July 31, 2025 06:23
@yiqingy0 yiqingy0 changed the title Fix merge waive list [Infra][TRTLLM-5633] - Fix merge waive list Jul 31, 2025
@yiqingy0 yiqingy0 requested a review from EmmaQiaoCh July 31, 2025 06:23
Signed-off-by: Yiqing Yan <[email protected]>
@yiqingy0 yiqingy0 force-pushed the fix_merge_waive_list branch from dfefd4c to ba1fc1d Compare July 31, 2025 06:25
@tensorrt-cicd
Copy link
Collaborator

PR_Github #13619 [ run ] completed with state FAILURE
/LLM/main/L0_MergeRequest_PR pipeline #10217 completed with status: 'ABORTED'

@yiqingy0
Copy link
Collaborator Author

/bot skip --comment "The merge waive list stage was tested in /LLM/main/L0_MergeRequest_PR pipeline #10217"

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13622 [ skip ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #13622 [ skip ] completed with state SUCCESS
Skipping testing for commit ba1fc1d

@yiqingy0 yiqingy0 merged commit d38c26b into NVIDIA:main Jul 31, 2025
4 checks passed
@yiqingy0 yiqingy0 deleted the fix_merge_waive_list branch July 31, 2025 06:58
lancelly pushed a commit to lancelly/TensorRT-LLM that referenced this pull request Aug 6, 2025
jain-ria pushed a commit to jain-ria/TensorRT-LLM that referenced this pull request Aug 7, 2025
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