-
Notifications
You must be signed in to change notification settings - Fork 1k
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
GPU tests pass when they probably shouldn't #1961
Comments
@nwnk, this behavior is expected. As there's no guarantee that GPU is present GPU tests report pass if no devices are available. |
If that were really expected, I would expect it to be consistent. In that OCL build, 7 gpu tests passed, but 156 failed. I don't understand why those seven ought to be different. |
Good point. I missed the fact that some tests still fail. Let me try to reproduce it. Do you see anything useful in failed tests output? |
It is really expected for the examples but not for the tests (gtests and benchdnn) because we only include examples in the binary releases (read oneAPI releases) so we don't want them to fail on systems that don't have GPUs. There is one example that fails (gpu_opencl_interop) but it's a bug in the error handling mechanism. |
Using the oneAPI 2024.1 release, build the SYCL CPU and GPU backends. Ensure that no SYCL devices are available on the system. Then run ctest:
If you try the same trick with the OCL backend, more things fail like they should, but there's still a few that xpass:
The text was updated successfully, but these errors were encountered: