Skip to content

Conversation

xinhe-nv
Copy link
Collaborator

@xinhe-nv xinhe-nv commented Sep 17, 2025

waive failed cases until fix is merged to main branch

Summary by CodeRabbit

  • Tests
    • Updated integration test waivers to skip four additional cases, including select multimodal quickstart scenarios and a serving benchmark.
    • Adjusts CI behavior by excluding these tests from execution until further notice.
    • No impact on application features or user workflows.

@xinhe-nv xinhe-nv marked this pull request as ready for review September 17, 2025 10:02
@xinhe-nv xinhe-nv enabled auto-merge (squash) September 17, 2025 10:02
@xinhe-nv
Copy link
Collaborator Author

/bot run --skip-test

@xinhe-nv xinhe-nv requested a review from liji-nv September 17, 2025 10:04
Copy link
Contributor

coderabbitai bot commented Sep 17, 2025

📝 Walkthrough

Walkthrough

Added four new SKIP entries to tests/integration/test_lists/waives.txt to skip specified multimodal E2E and benchmark tests, each annotated with corresponding nvbugs references.

Changes

Cohort / File(s) Summary of Changes
Test waivers updates
tests/integration/test_lists/waives.txt
Added 4 SKIP lines: 1) test_e2e.py::test_ptp_quickstart_multimodal[NVILA-8B-FP16-vila/NVILA-8B-image-False] (https://nvbugs/5509024), 2) test_e2e.py::test_ptp_quickstart_multimodal[qwen2.5-vl-7b-instruct-Qwen2.5-VL-7B-Instruct-video-False] (https://nvbugs/5509024), 3) test_e2e.py::test_ptp_quickstart_multimodal[qwen2.5-vl-7b-instruct-Qwen2.5-VL-7B-Instruct-video-True] (https://nvbugs/5509024), 4) test_e2e.py::test_trtllm_multimodal_benchmark_serving (https://nvbugs/5523315)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • crazydemo
  • LarryXFly

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The PR description is a single short sentence and does not follow the repository's required template; it lacks a detailed Description explaining the root cause and fix, a Test Coverage section naming the affected tests or waives entries, completion of the PR Checklist, and any ticket/NVBugs references, so it is incomplete for review. Please update the PR description to follow the template by adding a full Description of the issue and the proposed solution, a Test Coverage section listing the specific tests/waives.txt entries affected, a filled PR Checklist, and links to any related JIRA/NVBugs tickets plus any risk/rollback notes and the expected timeline for removing the waivers.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Title Check ✅ Passed The title "[TRTLLM-7250][fix] Add failed cases into waives.txt" accurately and concisely summarizes the primary change—adding failed test cases to tests/integration/test_lists/waives.txt—and includes a ticket reference and change type. It directly matches the changes in the PR and is clear enough for a teammate scanning history.
✨ Finishing touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
tests/integration/test_lists/waives.txt (2)

355-355: Benchmark serving waiver added—confirm blast radius.

If failures are isolated to certain backends or GPUs, consider scoping with the appropriate “full:/” prefix to avoid globally skipping this benchmark.


352-355: Optional: add light metadata to aid cleanup.

Consider appending a short note like “added 2025-09-17; owner: LLM QA” inside the parentheses after the bug link to make later un-waive sweeps easier. Many entries lack this, so treat as optional consistency improvement.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d3467f9 and 6fe0a81.

📒 Files selected for processing (1)
  • tests/integration/test_lists/waives.txt (1 hunks)
🧰 Additional context used
🧠 Learnings (5)
📓 Common learnings
Learnt from: tongyuantongyu
PR: NVIDIA/TensorRT-LLM#7781
File: tests/integration/test_lists/waives.txt:313-313
Timestamp: 2025-09-17T02:48:52.691Z
Learning: In TensorRT-LLM, `tests/integration/test_lists/waives.txt` is specifically for waiving/skipping tests, while other test list files like those in `test-db/` and `qa/` directories are for different test execution contexts (pre-merge, post-merge, QA tests). The same test appearing in both waives.txt and execution list files is intentional - the test is part of test suites but will be skipped due to the waiver.
📚 Learning: 2025-09-17T02:48:52.691Z
Learnt from: tongyuantongyu
PR: NVIDIA/TensorRT-LLM#7781
File: tests/integration/test_lists/waives.txt:313-313
Timestamp: 2025-09-17T02:48:52.691Z
Learning: In TensorRT-LLM, `tests/integration/test_lists/waives.txt` is specifically for waiving/skipping tests, while other test list files like those in `test-db/` and `qa/` directories are for different test execution contexts (pre-merge, post-merge, QA tests). The same test appearing in both waives.txt and execution list files is intentional - the test is part of test suites but will be skipped due to the waiver.

Applied to files:

  • tests/integration/test_lists/waives.txt
📚 Learning: 2025-09-09T09:40:45.658Z
Learnt from: fredricz-20070104
PR: NVIDIA/TensorRT-LLM#7645
File: tests/integration/test_lists/qa/llm_function_core.txt:648-648
Timestamp: 2025-09-09T09:40:45.658Z
Learning: In TensorRT-LLM test lists, it's common and intentional for the same test to appear in multiple test list files when they serve different purposes (e.g., llm_function_core.txt for comprehensive core functionality testing and llm_function_core_sanity.txt for quick sanity checks). This duplication allows tests to be run in different testing contexts.

Applied to files:

  • tests/integration/test_lists/waives.txt
📚 Learning: 2025-08-29T14:07:45.863Z
Learnt from: EmmaQiaoCh
PR: NVIDIA/TensorRT-LLM#7370
File: tests/unittest/trt/model_api/test_model_quantization.py:24-27
Timestamp: 2025-08-29T14:07:45.863Z
Learning: In TensorRT-LLM's CI infrastructure, pytest skip markers (pytest.mark.skip) are properly honored even when test files have __main__ blocks that call test functions directly. The testing system correctly skips tests without requiring modifications to the __main__ block execution pattern.

Applied to files:

  • tests/integration/test_lists/waives.txt
📚 Learning: 2025-07-28T17:06:08.621Z
Learnt from: moraxu
PR: NVIDIA/TensorRT-LLM#6303
File: tests/integration/test_lists/qa/examples_test_list.txt:494-494
Timestamp: 2025-07-28T17:06:08.621Z
Learning: In TensorRT-LLM testing, it's common to have both CLI flow tests (test_cli_flow.py) and PyTorch API tests (test_llm_api_pytorch.py) for the same model. These serve different purposes: CLI flow tests validate the traditional command-line workflow, while PyTorch API tests validate the newer LLM API backend. Both are legitimate and should coexist.

Applied to files:

  • tests/integration/test_lists/waives.txt
🔇 Additional comments (1)
tests/integration/test_lists/waives.txt (1)

352-354: Waivers present; test file not found — confirm test location & scope

  • The three waiver entries in tests/integration/test_lists/waives.txt (lines 352–354) each appear once.
  • rg returned "test_e2e.py: No such file or directory", so I could not verify that def test_ptp_quickstart_multimodal exists; confirm the test's filepath/name or update the waiver target. If the failures are platform-specific, restrict the waiver to the affected HW bucket to avoid over-skipping.

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18976 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #18976 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #14226 (Partly Tested) completed with status: 'SUCCESS'
Pipeline passed with automatic retried tests. Check the rerun report for details.

@xinhe-nv xinhe-nv force-pushed the user/qa/post_update_waive_20250917_LLM_FUNCTION_TEST_1327 branch from 6fe0a81 to 4187a46 Compare September 18, 2025 01:49
@xinhe-nv
Copy link
Collaborator Author

/bot reuse-pipeline

@xinhe-nv xinhe-nv changed the title [None][chore] Add failed cases into waives.txt [TRTLLM-7250][fix] Add failed cases into waives.txt Sep 18, 2025
@xinhe-nv
Copy link
Collaborator Author

/bot run --skip-test

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19071 [ reuse-pipeline ] triggered by Bot

@xinhe-nv
Copy link
Collaborator Author

/bot reuse-pipeline

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19075 [ reuse-pipeline ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19071 [ reuse-pipeline ] completed with state ABORTED
Can't reuse PR_Github #18976 (Partly Tested) with status: SUCCESS

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19073 [ run ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19075 [ reuse-pipeline ] completed with state ABORTED
Can't reuse PR_Github #18976 (Partly Tested) with status: SUCCESS

@xinhe-nv
Copy link
Collaborator Author

/bot reuse-pipeline --number 18976

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19085 [ reuse-pipeline ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19073 [ run ] completed with state ABORTED
LLM/main/L0_MergeRequest_PR #14312 (Blue Ocean) completed with status: ABORTED

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19085 [ reuse-pipeline ] completed with state SUCCESS
Can't reuse PR_Github #19073 (Partly Tested) with status: ABORTED

@xinhe-nv
Copy link
Collaborator Author

/bot help

Copy link

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.

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.

@xinhe-nv
Copy link
Collaborator Author

/bot run --reuse-test pipeline-id 18976

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19089 Bot args parsing error: usage: /bot run [--reuse-test [optionalpipeline-id]] [--disable-fail-fast]
[--skip-test] [--stage-list "A10-PyTorch-1, xxx"]
[--gpu-type "A30, H100_PCIe"] [--test-backend "pytorch, cpp"]
[--multi-gpu-test] [--add-multi-gpu-test]
[--only-multi-gpu-test] [--disable-multi-gpu-test]
[--post-merge]
[--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx"]
[--debug] [--detailed-log]
/bot run: error: argument --reuse-test/--disable-reuse-test: invalid int value: 'pipeline-id'

@xinhe-nv
Copy link
Collaborator Author

/bot run --reuse-test 18976

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19093 [ run ] triggered by Bot

@xinhe-nv xinhe-nv force-pushed the user/qa/post_update_waive_20250917_LLM_FUNCTION_TEST_1327 branch 2 times, most recently from bae24a3 to 51039e6 Compare September 18, 2025 04:00
@tensorrt-cicd
Copy link
Collaborator

PR_Github #19093 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #14324 completed with status: 'SUCCESS'
Pipeline passed with automatic retried tests. Check the rerun report for details.

@xinhe-nv xinhe-nv force-pushed the user/qa/post_update_waive_20250917_LLM_FUNCTION_TEST_1327 branch from 51039e6 to e84743f Compare September 18, 2025 06:22
@xinhe-nv
Copy link
Collaborator Author

/bot reuse-pipeline

Signed-off-by: xinhe-nv <[email protected]>
@xinhe-nv xinhe-nv force-pushed the user/qa/post_update_waive_20250917_LLM_FUNCTION_TEST_1327 branch from e84743f to 3b13c01 Compare September 18, 2025 06:25
@tensorrt-cicd
Copy link
Collaborator

PR_Github #19121 [ reuse-pipeline ] triggered by Bot

@tensorrt-cicd
Copy link
Collaborator

PR_Github #19121 [ reuse-pipeline ] completed with state SUCCESS
Reusing PR_Github #19093 for commit 3b13c01

@xinhe-nv xinhe-nv merged commit 236f71e into NVIDIA:main Sep 18, 2025
5 checks passed
@xinhe-nv xinhe-nv deleted the user/qa/post_update_waive_20250917_LLM_FUNCTION_TEST_1327 branch September 18, 2025 07:27
Wong4j pushed a commit to Wong4j/TensorRT-LLM that referenced this pull request Sep 20, 2025
MrGeva pushed a commit to nv-auto-deploy/TensorRT-LLM that referenced this pull request Sep 21, 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