-
Notifications
You must be signed in to change notification settings - Fork 112
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
CTS tests failing on multi-device scenarios #1063
Milestone
Comments
This does remind me of a recent PR, to append the device index to the test name but I'm struggling to find where that was being discussed... |
Yup, that is the problem this PR is trying to fix: #992 |
This has probably already been resolved in another PR, will need to check that. |
Yes, #1805, we added multi-device PVC testing some time ago and were forced to fix it :) |
Thanks, closing since its already fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running a CTS in a multi-device system, I see errors like:
the problem seem to be here
https://github.com/oneapi-src/unified-runtime/blob/adapters/test/conformance/testing/include/uur/fixtures.h#L97
::testing::ValuesIn(uur::DevicesEnvironment::instance->devices), \
where the name for tests are created for a set of devices, so if we have multiple devices with the same name, then test aborts.
WA at least for L0- for now is to use ZE_AFFINITY_MASK=0 to select only the first device.
@kbenzie , @pbalcer : are we aware of this? is there a way of fixing it w/o requiring the use of the affinity mask, or in the future, of the ONEAPI_DEVICE_SELECTOR?
The text was updated successfully, but these errors were encountered: