Skip to content

Conversation

xinhe-nv
Copy link
Collaborator

@xinhe-nv xinhe-nv commented Jul 23, 2025

waive failed cases.

Summary by CodeRabbit

  • Tests
    • Added six new tests to the skip list, each annotated with a relevant bug tracking URL. This affects specific tests in accuracy and end-to-end test suites.

@xinhe-nv xinhe-nv requested review from crazydemo and LarryXFly July 23, 2025 08:53
Copy link
Contributor

coderabbitai bot commented Jul 23, 2025

Walkthrough

Six new test cases are added to the skip list in tests/integration/test_lists/waives.txt. These include three tests from accuracy/test_llm_api_pytorch.py and three from test_e2e.py, each annotated with a unique NVIDIA bug tracking URL. No other files or entries are modified.

Changes

File(s) Change Summary
tests/integration/test_lists/waives.txt Added six new test skip entries for specific test cases, each with a corresponding NVIDIA bug URL.

Estimated code review effort

1 (~2 minutes)

Possibly related PRs

Suggested reviewers

  • crazydemo
  • LarryXFly

Poem

Six tests now hop past the nightly run,
With waivers in place till debugging is done.
Bug links in tow, they quietly sleep,
While coders and rabbits their vigil keep.
🐇✨

Skipping along, the tests take a rest,
Until they're fixed and return to the quest!


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

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

431-436: (Optional) Keep the waive list easier to scan by grouping new entries with their source file peers.
Consider inserting the three accuracy/test_llm_api_pytorch.py waives right after the existing waives for that file (around line 388) and the three test_e2e.py waives near the other test_e2e.py blocks (~232, 391). This keeps related tests clustered and speeds up look-ups during triage.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ed62a06 and 3b0d6b2.

📒 Files selected for processing (1)
  • tests/integration/test_lists/waives.txt (1 hunks)
🧠 Learnings (2)
📓 Common learnings
Learnt from: yiqingy0
PR: NVIDIA/TensorRT-LLM#5198
File: jenkins/mergeWaiveList.py:0-0
Timestamp: 2025-07-22T08:33:49.076Z
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.
tests/integration/test_lists/waives.txt (1)

Learnt from: yiqingy0
PR: #5198
File: jenkins/mergeWaiveList.py:0-0
Timestamp: 2025-07-22T08:33:49.076Z
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.

🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: yiqingy0
PR: NVIDIA/TensorRT-LLM#5198
File: jenkins/mergeWaiveList.py:0-0
Timestamp: 2025-07-22T08:33:49.076Z
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.
tests/integration/test_lists/waives.txt (1)

Learnt from: yiqingy0
PR: #5198
File: jenkins/mergeWaiveList.py:0-0
Timestamp: 2025-07-22T08:33:49.076Z
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.

⏰ 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)

431-436: All six newly-waived tests conform to the expected “:: SKIP ()” format – LGTM.
No duplicate entries for these tests are present elsewhere in the list, and each line has the mandatory bug‐tracking URL.

Signed-off-by: xinhe-nv <[email protected]>
@xinhe-nv xinhe-nv changed the title Draft: test: [CI] Add failed cases into waives.txt test: [CI] Add failed cases into waives.txt Jul 23, 2025
@xinhe-nv xinhe-nv marked this pull request as ready for review July 23, 2025 09:01
@xinhe-nv xinhe-nv enabled auto-merge (squash) July 23, 2025 09:01
@xinhe-nv
Copy link
Collaborator Author

/bot run

@LarryXFly LarryXFly disabled auto-merge July 23, 2025 09:04
@LarryXFly LarryXFly merged commit 2b0fa24 into NVIDIA:main Jul 23, 2025
2 of 3 checks passed
@xinhe-nv xinhe-nv deleted the user/qa/post_update_waive_20250723_LLM_FUNCTION_TEST_DEBUG_1439 branch July 23, 2025 09:06
@tensorrt-cicd
Copy link
Collaborator

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

lancelly pushed a commit to lancelly/TensorRT-LLM that referenced this pull request Aug 6, 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