-
Notifications
You must be signed in to change notification settings - Fork 31.2k
fix(DPT,Depth-Anything) Address expected_slice errors inside inference tests #34518
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
Conversation
…e tests Signed-off-by: Phillip Kuznetsov <[email protected]>
|
@philkuz run-slow commit should be after the run-slow label is added, can you please push it once again? |
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
0510da7 to
771d51e
Compare
Done! |
qubvel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix! The tests are green now!
cc @ydshieh for tests change
|
Yes, great! (And thank you for requesting/triggering the slow tests!) |
|
Thanks all!!
…On Thu, Oct 31, 2024 at 8:48 AM Yih-Dar ***@***.***> wrote:
Merged #34518 <#34518>
into main.
—
Reply to this email directly, view it on GitHub
<#34518 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJUBEYVPVLGOCSEQVXGMZDZ6JGMHAVCNFSM6AAAAABQ4XLOP2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGAZTSNZTGQ4TEMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
…e tests (huggingface#34518) * fix(DPT,Depth-Anything) Address expected_slice errors inside inference tests Signed-off-by: Phillip Kuznetsov <[email protected]> * [run_slow] dpt, depth_anything --------- Signed-off-by: Phillip Kuznetsov <[email protected]>
What does this PR do?
Fixes slow tests that are broken in main and discovered in this PR: #34103
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines, and
here are tips on formatting docstrings.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@qubvel