[https://nvbugs/5444095][infra] waive test_ptp_quickstart_multimodal llava test

[yechank-nvidia]

Summary by CodeRabbit

• Tests
  • Updated test skip configuration to temporarily exclude a specific end-to-end multimodal quickstart scenario affected by a known issue, improving CI reliability, build stability, and reducing false failures during automated runs. This change is limited to test infrastructure and does not alter product functionality or user experience. No other tests were modified, and no user-facing behavior is impacted.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new SKIP waiver entry in tests/integration/test_lists/waives.txt for a specific parameterization of test_e2e.py::test_ptp_quickstart_multimodal tied to nvbugs/5444095. No other files or test entries were changed.

Changes

Cohort / File(s)	Summary of Changes
Waivers list update tests/integration/test_lists/waives.txt	Added SKIP waiver for test_e2e.py::test_ptp_quickstart_multimodal[llava-v1.6-mistral-7b-llava-v1.6-mistral-7b-hf-image-False] with nvbugs/5444095.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• [nvbug/5409417] Unwaive llava test case #6460: Touches the same waiver entry for the same test parameterization (adds vs removes SKIP), directly related.
• [TRTQA-2920][fix] Add failed cases into waives.txt #6719: Adds the same SKIP entry plus additional waivers in the same file.
• Waive tests #6312: Modifies the same skip list for similar test_ptp_quickstart_multimodal cases (different variants/bug IDs).

Suggested reviewers

• venkywonka
• yiqingy0

---

📜 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 824feb8 and abc3c6a.

📒 Files selected for processing (1)

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

🧰 Additional context used

🧠 Learnings (1)

📚 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 (2)

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

289-289: Waiver entry looks correct and consistent.

Node id format, SKIP keyword, and nvbugs link match existing conventions in this file. No nits.

---

289-289: Confirming Pytest Node ID Accuracy

All checks pass:

• The waiver entry in tests/integration/test_lists/waives.txt at line 289 exactly matches the pytest‐generated node ID
• There are no duplicate waiver entries
• The parameter values (llava-v1.6-mistral-7b, llava-v1.6-mistral-7b-hf, image, False) align with the pytest.mark.parametrize setup in tests/integration/defs/test_e2e.py

Recommended next steps:

• If this skip should only apply to certain hardware or driver versions, consider scoping it (e.g., full:GH200/...) rather than a global skip
• Otherwise, the waiver can remain as is

✨ Finishing Touches

🧪 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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
• 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.

[yuxianq]

/bot run

[tensorrt-cicd]

PR_Github #14803 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #14803 [ run ] completed with state SUCCESS
/LLM/release-1.0/L0_MergeRequest_PR pipeline #56 completed with status: 'SUCCESS'