-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[tests] make tests device-agnostic (part 4) #10508
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: hlky <hlky@hlky.ac>
Co-authored-by: hlky <hlky@hlky.ac>
Co-authored-by: hlky <hlky@hlky.ac>
Co-authored-by: hlky <hlky@hlky.ac>
Co-authored-by: hlky <hlky@hlky.ac>
Co-authored-by: hlky <hlky@hlky.ac>
Co-authored-by: hlky <hlky@hlky.ac>
Hi @sayakpaul @hlky @DN6 , could we proceed with this PR? Thx a lot! |
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 very nuch. Just a single comment for clarification.
@@ -101,7 +102,7 @@ def tearDown(self): | |||
# Keeping this test here makes sense because it doesn't look any integration | |||
# (value assertions on logits). | |||
@slow | |||
@require_torch_gpu | |||
@require_torch_accelerator |
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.
Do we need to condition the assertion slices based on the accelerator being used?
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.
Yes, we might need to do so. But I plan to submit a follow-up PR for value assertion related issues. Because we need to investigate whether this is not a bug in our own software stack.
What does this PR do?
Follow up of PR #10437