You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've added a TODO in the CTS for urUSMDevice/Shared/HostAlloc InvalidUSMSize tests for producing a UR_RESULT_ERROR_INVALID_USM_SIZE error. The condition of size is greater than UR_DEVICE_INFO_MAX_MEM_ALLOC_SIZE is currently uncovered:
Looks like it's caused a bunch of fails, probably due to known issues with implementing UR_DEVICE_INFO_MAX_MEM_ALLOC_SIZE. I think we might just need to omit testing the upper limit on this one and let the return code be a "possible" one rather than mandatory.
I've added a TODO in the CTS for urUSMDevice/Shared/HostAlloc
InvalidUSMSize
tests for producing aUR_RESULT_ERROR_INVALID_USM_SIZE
error. The condition ofsize is greater than UR_DEVICE_INFO_MAX_MEM_ALLOC_SIZE
is currently uncovered:Originally posted by @aarongreig in #2642 (comment)
The text was updated successfully, but these errors were encountered: