Skip to content

Conversation

@xinhe-nv
Copy link
Collaborator

@xinhe-nv xinhe-nv commented Aug 26, 2025

waive failed cases.

Summary by CodeRabbit

  • Tests
    • Expanded waiver list to skip numerous scenarios across multimodal, privacy-sensitive model variants, quantization, accuracy checks (CLI/API), and end-to-end quickstart flows.
    • Added nvbugs-linked annotations to skipped entries for traceability and clearer CI signaling.
    • Note: the same skip block was inserted twice, producing duplicated entries in the waiver list.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 26, 2025

📝 Walkthrough

Walkthrough

Adds a large block of SKIP directives to tests/integration/test_lists/waives.txt, marking numerous integration tests as skipped with nvbugs references; the identical SKIP block is inserted twice, creating duplicated entries.

Changes

Cohort / File(s) Summary of Changes
Test waivers list updates
tests/integration/test_lists/waives.txt
Appends many SKIP directives for multimodal, phi, accuracy (CLI/LLM API), and end-to-end quickstart tests with nvbugs URLs; the identical SKIP block appears twice (duplicated insertion).

Sequence Diagram(s)

(omitted — changes are file-level test skip additions with no control-flow or runtime behavior changes)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • crazydemo
  • LarryXFly

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 10bced5 and 873dde0.

📒 Files selected for processing (1)
  • tests/integration/test_lists/waives.txt (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • 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
✨ 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
🪧 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.
    • 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.
  • 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 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/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

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

♻️ Duplicate comments (1)
tests/integration/test_lists/waives.txt (1)

1-330: Context note: duplicating waivers across CLI flow and LLM API is legitimate.

Referencing our prior learning for this repo: it’s expected to maintain both CLI flow tests and PyTorch LLM API tests for the same model; they serve different purposes. No action needed — mentioning to preempt questions.

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

331-333: Multimodal fuyu/llava waivers look consistent; keep bug-link format uniform.

Entries are well-scoped (bs:8, True/False cpp_e2e variants). Minor nit: bug links oscillate between nvbugs and nvbugspro across the file. If there’s a preferred canonical form, standardize when convenient.


331-355: Optional: add owner/date metadata to speed future un-waive sweeps.

If the parser tolerates inline metadata, appending “; owner=xinhe-nv; added=2025-08-26” inside the reason parentheses makes expiry and ownership explicit. Example for a single line:

-examples/test_phi.py::test_llm_phi_quantization_1gpu[Phi-3-mini-128k-instruct-fp8-float16] SKIP (https://nvbugs/5465143)
+examples/test_phi.py::test_llm_phi_quantization_1gpu[Phi-3-mini-128k-instruct-fp8-float16] SKIP (https://nvbugs/5465143; owner=xinhe-nv; added=2025-08-26)

If you prefer, I can bulk-apply this style to the new block.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 23ed0c8 and 5e38097.

📒 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
⏰ 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 (4)
tests/integration/test_lists/waives.txt (4)

352-354: Waivers validated: no overlapping quickstart entries

  • Existing non-chunked 8-GPU waivers at lines 234–235
  • New chunked_prefill_sq_22k entries at lines 352–354 are distinct

334-341: Verify NVBUGS/5465143 scope across all Phi skips

It looks like all Phi-related skips point to NVBUGS/5465143, except one non-Phi test:

• Lines 334–337, 338–339, 341:
– examples/test_phi.py::{lora, quantization variants}
– accuracy/test_cli_flow.py::TestPhi4MiniInstruct::{test_auto_dtype, test_tp2}
– accuracy/test_llm_api.py::TestPhi4MiniInstruct::test_fp8
→ SKIP (https://nvbugs/5465143)

• Line 340: accuracy/test_cli_flow.py::TestLongAlpaca7B::test_auto_dtype
→ SKIP (https://nvbugs/5481075) — this one’s for a different model and bug.

Please confirm that NVBUGS/5465143 truly covers all of the Phi modalities (LoRA, quantization, CLI flow, LLM API). If it does, no action is needed; if not, split the Phi-focused skips by their actual root causes to simplify future cleanup.


331-355: All new waiver entries are unique; ready to merge.

Verified that no duplicate nodeids exist in tests/integration/test_lists/waives.txt and that every entry in lines 331–355 appears exactly once. Ship it.


342-351: All GPTOSS and EXAONE4 nodeids verified—no typos detected

The TestGPTOSS class (line 2684) defines both test_w4_1gpu and test_w4_4gpus with the exact parameter IDs used in the waivers (True-True-cutlass, True-True-trtllm, tp4-CUTLASS, tp4-TRTLLM, ep4-CUTLASS, ep4-TRTLLM, dp4-CUTLASS, dp4-TRTLLM), and the TestEXAONE4::test_auto_dtype method (line 2795) exists as specified. No mismatches or stale entries were found—these skips correctly target existing tests.

@xinhe-nv xinhe-nv marked this pull request as ready for review August 26, 2025 08:55
@xinhe-nv xinhe-nv enabled auto-merge (squash) August 26, 2025 08:55
Signed-off-by: xinhe-nv <[email protected]>
Signed-off-by: Xin He (SW-GPU) <[email protected]>
@xinhe-nv xinhe-nv force-pushed the user/qa/post_update_waive_20250826_DEBUG_LLM_FUNCTION_TEST_1662 branch from 10bced5 to 873dde0 Compare August 26, 2025 09:11
@xinhe-nv
Copy link
Collaborator Author

/bot run

@LarryXFly LarryXFly disabled auto-merge August 26, 2025 09:13
@LarryXFly LarryXFly merged commit 80043af into NVIDIA:main Aug 26, 2025
2 checks passed
@tensorrt-cicd
Copy link
Collaborator

PR_Github #16542 [ ] completed with state FAILURE
Not allowed on merged PR

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