[None][chore] Add failed cases into waives.txt

[xinhe-nv]

waive failed cases.

Summary by CodeRabbit

• Tests
  • Updated test skip list to exclude a specific test case from execution.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[xinhe-nv]

/bot run --skip-test

[coderabbitai]

📝 Walkthrough

Walkthrough

A single test case entry is added to the test waiver list, marking a specific Llama 3.1 8B instruction test for skipping due to an identified issue.

Changes

Cohort / File(s)	Summary
Test Waiver List tests/integration/test_lists/waives.txt	Added SKIP entry for TestLlama3_1_8BInstruct::test_ctx_pp_gen_tp_asymmetric[MMLU-gen_tp=1-ctx_pp=2] test case in sm89 accuracy serving tests with bug reference #5596337

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• NVIDIA/TensorRT-LLM#10129: Adds SKIP entries to the same waives.txt file for TestLlama3_1_8BInstruct test cases.
• NVIDIA/TensorRT-LLM#9588: Modifies the same test waiver list by adding multiple SKIP entries for failing integration tests.
• NVIDIA/TensorRT-LLM#10025: Updates tests/integration/test_lists/waives.txt with additional SKIP entries for integration test cases.

Suggested reviewers

• crazydemo
• LarryXFly
• jieli-matrix

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is too minimal. It lacks detailed explanation of what, why, test coverage section, and required checklist completion.	Expand the description to include the affected test case details, reason for waiving, affected systems, and complete the PR checklist items as applicable.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding failed test cases to the waives.txt file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent 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 92d90fa and 3a02085.

📒 Files selected for processing (1)

• tests/integration/test_lists/waives.txt

🧰 Additional context used

🧠 Learnings (7)

📓 Common learnings

Learnt from: tongyuantongyu
Repo: NVIDIA/TensorRT-LLM PR: 7781
File: tests/integration/test_lists/waives.txt:313-313
Timestamp: 2025-09-17T02:48:52.732Z
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.

Learnt from: fredricz-20070104
Repo: NVIDIA/TensorRT-LLM PR: 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.

📚 Learning: 2025-09-17T02:48:52.732Z

Learnt from: tongyuantongyu
Repo: NVIDIA/TensorRT-LLM PR: 7781
File: tests/integration/test_lists/waives.txt:313-313
Timestamp: 2025-09-17T02:48:52.732Z
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
Repo: NVIDIA/TensorRT-LLM PR: 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-07-22T08:33:49.109Z

Learnt from: yiqingy0
Repo: NVIDIA/TensorRT-LLM PR: 5198
File: jenkins/mergeWaiveList.py:0-0
Timestamp: 2025-07-22T08:33:49.109Z
Learning: In the TensorRT-LLM waive list merging system, removed lines are always located at the end of the merge waive lists, which is why the mergeWaiveList.py script uses reverse traversal - it's an optimization for this specific domain constraint.

Applied to files:

• tests/integration/test_lists/waives.txt

📚 Learning: 2025-08-29T14:07:45.863Z

Learnt from: EmmaQiaoCh
Repo: NVIDIA/TensorRT-LLM PR: 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-08-26T09:49:04.956Z

Learnt from: pengbowang-nv
Repo: NVIDIA/TensorRT-LLM PR: 7192
File: tests/integration/test_lists/test-db/l0_dgx_b200.yml:56-72
Timestamp: 2025-08-26T09:49:04.956Z
Learning: In TensorRT-LLM test configuration files, the test scheduling system handles wildcard matching with special rules that prevent duplicate test execution even when the same tests appear in multiple yaml files with overlapping GPU wildcards (e.g., "*b200*" and "*gb200*").

Applied to files:

• tests/integration/test_lists/waives.txt

📚 Learning: 2025-07-28T17:06:08.621Z

Learnt from: moraxu
Repo: NVIDIA/TensorRT-LLM PR: 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

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Pre-commit Check

🔇 Additional comments (1)

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

502-502: ✓ LGTM!

The test waiver entry follows the established format and naming conventions. The entry represents a valid parameter variant of an existing waived test and correctly references the issue tracker, consistent with similar entries in the file.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[tensorrt-cicd]

PR_Github #29672 [ run ] triggered by Bot. Commit: 3a02085

[tensorrt-cicd]

PR_Github #29672 [ run ] completed with state SUCCESS. Commit: 3a02085
/LLM/main/L0_MergeRequest_PR pipeline #22790 (Partly Tested) completed with status: 'SUCCESS'

[xinhe-nv]

/bot reuse-pipeline

[tensorrt-cicd]

PR_Github #29736 [ reuse-pipeline ] triggered by Bot. Commit: 891a35a

[tensorrt-cicd]

PR_Github #29736 [ reuse-pipeline ] completed with state SUCCESS. Commit: 891a35a
Reusing PR_Github #29672 (Partly Tested) for commit 891a35a

[xinhe-nv]

/bot reuse-pipeline

[tensorrt-cicd]

PR_Github #29743 [ reuse-pipeline ] triggered by Bot. Commit: 2ece3a4

[xinhe-nv]

/bot reuse-pipeline

[tensorrt-cicd]

PR_Github #29752 [ reuse-pipeline ] triggered by Bot. Commit: a65f4c3

[tensorrt-cicd]

PR_Github #29743 [ reuse-pipeline ] completed with state ABORTED. Commit: 2ece3a4
Can't reuse PR_Github #29672 (Partly Tested) with status: SUCCESS

[tensorrt-cicd]

PR_Github #29752 [ reuse-pipeline ] completed with state SUCCESS. Commit: a65f4c3
Reusing PR_Github #29672 (Partly Tested) for commit a65f4c3