[Infra] - Waive failed tests in post-merge

[EmmaQiaoCh]

Summary by CodeRabbit

• Tests
  • Added several tests to the skip list due to known issues, each linked to a specific bug tracking URL.
  • Marked the test_nemotron_nas_lora test to be skipped, referencing a related bug.

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.

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

This change adds several new test cases to the skip list in waives.txt, each linked to a specific NVIDIA bug. Additionally, a unit test in test_llm_pytorch.py is now skipped using a pytest decorator, also referencing a bug. No existing skip entries or test logic were altered.

Changes

File(s)	Change Summary
tests/integration/test_lists/waives.txt	Added multiple new test skip entries, each referencing an NVIDIA bug for the skip reason.
tests/unittest/llmapi/test_llm_pytorch.py	Added pytest.mark.skip decorator to test_nemotron_nas_lora with a bug-tracking skip reason.

Sequence Diagram(s)

sequenceDiagram
    participant TestRunner
    participant waives.txt
    participant test_llm_pytorch.py

    TestRunner->>waives.txt: Check skip list before running integration tests
    waives.txt-->>TestRunner: Indicate tests to skip (with bug URLs)
    TestRunner->>test_llm_pytorch.py: Discover test_nemotron_nas_lora
    test_llm_pytorch.py-->>TestRunner: @pytest.mark.skip with bug URL
    TestRunner-->>TestRunner: Skip marked tests during execution

Loading

Possibly related PRs

• [Infra] - Add wiave list for pytest when using slurm #6130: Adds infrastructure for handling the waives.txt skip list during multi-node test runs.
• fix: Fix DeepSeek R1 CI #6129: Modifies and removes skip entries for tests in accuracy/test_llm_api_pytorch.py, related to test skip management.
• [https://nvbugs/5387375] fix(scaffolding): fix scaffolding aime test in test_e2e #6140: Addresses the same test and bug in test_e2e.py as this PR, but by fixing rather than skipping.

Suggested reviewers

• niukuo
• chzblych

Poem

In the warren of tests, a bunny did hop,
Marking some trials with a "please do not stop."
Skipped for a bug, with a URL in tow,
The rabbit keeps track of which tests not to show.
🐇✨

---

📜 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 a95f31e and da92f96.

📒 Files selected for processing (2)

• tests/integration/test_lists/waives.txt (1 hunks)
• tests/unittest/llmapi/test_llm_pytorch.py (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

tests/unittest/llmapi/test_llm_pytorch.py (1)

Learnt from: amitz-nv
PR: NVIDIA/TensorRT-LLM#5616
File: tensorrt_llm/executor/worker.py:375-384
Timestamp: 2025-07-17T09:01:27.374Z
Learning: In tensorrt_llm/executor/worker.py, the LoRA adapter cache optimization logic that checks `is_adapter_in_cpu_cache()` and conditionally passes None for weights/config has a known race condition issue that cannot be solved with simple error handling or verification checks. This is a known limitation that requires a more comprehensive solution.

🔇 Additional comments (2)

tests/integration/test_lists/waives.txt (1)

441-450: LGTM! Proper test skip entries with bug tracking.

The new test skip entries are well-formatted and consistently follow the established pattern. Each entry includes appropriate bug tracking URLs for accountability and future reference.

tests/unittest/llmapi/test_llm_pytorch.py (1)

257-257: LGTM! Proper test skip with bug tracking reference.

The pytest skip decorator is correctly applied with an appropriate bug tracking reference. This aligns with the infrastructure changes for managing failing tests in the post-merge pipeline.

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

[EmmaQiaoCh]

/bot skip --comment "Skip failed tests"

[tensorrt-cicd]

PR_Github #12305 [ skip ] triggered by Bot

[tensorrt-cicd]

PR_Github #12305 [ skip ] completed with state SUCCESS
Skipping testing for commit da92f96