-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Correcting Misleading Test Skip Reasons. #7808
Conversation
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
@drivanov pls fix the lint check failure first. |
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
@mfbalin could you please take another round of review? |
Not authorized to trigger CI. Please ask core developer to help trigger via issuing comment:
|
Description
This PR is similar to PR#7749 and it addresses the following warnings
These warnings occur when certain GraphBolt tests are run on a CPU (
F._default_context_str != "GPU"
) on a machine with a GPU withdevice_capability=8
.Checklist
Please feel free to remove inapplicable items for your PR.
Changes