-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[None][chore] Add failed cases into waives.txt #8004
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[None][chore] Add failed cases into waives.txt #8004
Conversation
e9097db to
ccd0943
Compare
|
/bot run --skip-test |
📝 WalkthroughWalkthroughAdded a skip entry in tests/integration/test_lists/waives.txt for accuracy/test_llm_api_pytorch.py::TestMistralSmall24B::test_auto_dtype under the full:A100 context, referencing an nvbugs link. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (4)📓 Common learnings📚 Learning: 2025-09-17T02:48:52.732ZApplied to files:
📚 Learning: 2025-08-29T14:07:45.863ZApplied to files:
📚 Learning: 2025-08-26T09:49:04.956ZApplied to files:
⏰ 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)
🔇 Additional comments (1)
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. 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. Comment |
|
PR_Github #20020 [ run ] triggered by Bot |
ccd0943 to
1e4990a
Compare
|
PR_Github #20020 [ run ] completed with state |
1e4990a to
5a30b28
Compare
5a30b28 to
6a085c3
Compare
|
/bot reuse-pipeline |
|
PR_Github #20050 [ reuse-pipeline ] triggered by Bot |
|
PR_Github #20050 [ reuse-pipeline ] completed with state |
Signed-off-by: xinhe-nv <[email protected]>
Signed-off-by: xinhe-nv <[email protected]>
6a085c3 to
cc818e1
Compare
|
/bot reuse-pipeline |
|
PR_Github #20061 [ reuse-pipeline ] triggered by Bot |
|
PR_Github #20061 [ reuse-pipeline ] completed with state |
waive failed cases.
Summary by CodeRabbit