Skip to content

[SYCL][CUDA] Skip PiCudaTests when running other plugins #4103

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

Merged
merged 1 commit into from
Jul 15, 2021

Conversation

npmiller
Copy link
Contributor

This fixes an issue where if the cuda plugin is enabled and lit tests
for another plugin are run, it will try to run PiCudaTests, and all of
them will assert since the device filter will be set to a non-cuda
plugin and the tests request a cuda device.

So instead of asserting this patch makes the PiCudaTests get marked as
skipped if there is no cuda device found.

@npmiller npmiller requested a review from a team as a code owner July 14, 2021 12:12
@npmiller npmiller requested a review from smaslov-intel July 14, 2021 12:12
This fixes an issue where if the cuda plugin is enabled and lit tests
for another plugin are run, it will try to run PiCudaTests, and all of
them will assert since the device filter will be set to a non-cuda
plugin and the tests request a cuda device.

So instead of asserting this patch makes the PiCudaTests get marked as
skipped if there is no cuda device found.
Copy link
Contributor

@smaslov-intel smaslov-intel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@bader bader changed the title [SYCL] Skip PiCudaTests when running other plugins [SYCL][CUDA] Skip PiCudaTests when running other plugins Jul 15, 2021
@bader bader merged commit f837d17 into intel:sycl Jul 15, 2021
@bader bader added the cuda CUDA back-end label Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cuda CUDA back-end
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants