Update boxes expectations for OWLViT test #40030
Open
+4
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
[For maintainers] Suggested jobs to run (before merge) run-slow: owlvit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
While working on a related PR #40023, I noticed some OWLViT tests were failing on main on my local machine.
Seems to be some minor differences in the predicted boxes so I simply updated them to the latest values (the other outputs seem correct).
Not sure if this is hardware-related or something that slipped through at some point - I'm running on a RTX 4080 SUPER on WSL (pip torch 2.7.1 cuda 12.6, os cuda version 12.9)
Before submitting
Who can review?
Maybe @amyeroberts @qubvel @ArthurZucker