-
Notifications
You must be signed in to change notification settings - Fork 199
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
Added new cl_khr_semaphore tests to verify clReleaseSemaphoreKHR/clRetainSemaphoreKHR negative results #1976
Added new cl_khr_semaphore tests to verify clReleaseSemaphoreKHR/clRetainSemaphoreKHR negative results #1976
Conversation
-clReleaseSemaphoreKHR -clRetainSemaphoreKHR
// Release invalid semaphore | ||
cl_int err = CL_SUCCESS; | ||
err = clReleaseSemaphoreKHR(nullptr); | ||
test_failure_error(err, CL_INVALID_SEMAPHORE_KHR, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor: this will print "expected (unknown)" because harness/errorHelpers.cpp does not know that CL_INVALID_SEMAPHORE_KHR exists.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, other than @paulfradgley 's comment, which is more of a nice-to-have since the error message will not be printed unless the test fails.
2024/07/02 teleconference: @shajder Could you rebase/resolve conflicts please? |
…on for unexpected result log
Merging as discussed in memory subgroup call of July 9th 2024. |
According to work plan from issue #1691