[nvbugs/5414909] fix: Qwen2-VL keyword on L20

[yechank-nvidia]

This PR fixes the bug of Qwen2-VL's keyword on L20

Summary by CodeRabbit

• Tests
  • Updated the expected keywords for image outputs in the "qwen2-vl-7b-instruct" model's end-to-end test.

[coderabbitai]

📝 Walkthrough

Walkthrough

The expected keywords for the "qwen2-vl-7b-instruct" model in the "image" modality were updated in the test_ptp_quickstart_multimodal test within tests/integration/defs/test_e2e.py. No other code or logic changes were introduced.

Changes

Cohort / File(s)	Change Summary
Test keyword update tests/integration/defs/test_e2e.py	Modified the list of expected keywords for the "qwen2-vl-7b-instruct" model in the image modality.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• test: [CI] remove closed bugs #6381: Updates skip entries for various multimodal tests including test_ptp_quickstart_multimodal but does not change expected outputs.
• [fix] Fix flaky mistral E2E test #6230: Modifies expected keyword lists in the same test function test_ptp_quickstart_multimodal but for different models and keywords.

Suggested reviewers

• liji-nv
• venkywonka

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 eb75d56 and d9f4f59.

📒 Files selected for processing (1)

• tests/integration/defs/test_e2e.py (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• tests/integration/defs/test_e2e.py

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

🧪 Generate unit tests

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

---

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

[yechank-nvidia]

/bot run

[tensorrt-cicd]

PR_Github #13267 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #13267 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9908 completed with status: 'FAILURE'

[yechank-nvidia]

/bot run

[tensorrt-cicd]

PR_Github #13351 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #13351 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #9982 completed with status: 'FAILURE'

[yechank-nvidia]

/bot run

[tensorrt-cicd]

PR_Github #13442 [ run ] triggered by Bot

[tensorrt-cicd]

PR_Github #13442 [ run ] completed with state SUCCESS
/LLM/main/L0_MergeRequest_PR pipeline #10059 completed with status: 'SUCCESS'

[QiJune]

LGTM