-
Notifications
You must be signed in to change notification settings - Fork 205
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
Command-buffer queue compatibility test update #2230
base: main
Are you sure you want to change the base?
Conversation
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.
One additional note - I believe the negative_enqueue_queue_not_compatible
test is invalid now, and can be removed.
test_conformance/extensions/cl_khr_command_buffer/command_buffer_queue_substitution.cpp
Outdated
Show resolved
Hide resolved
test_conformance/extensions/cl_khr_command_buffer/command_buffer_queue_substitution.cpp
Show resolved
Hide resolved
d293fcc
to
9c663aa
Compare
Update cl_khr_command_buffer tests to reflect changes from KhronosGroup/OpenCL-Docs#1292 Required headers change KhronosGroup/OpenCL-Headers#271 to enable tests with version 0.9.7
9c663aa
to
5999c5a
Compare
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.
The new tests LGTM.
I still think the negative_enqueue_queue_not_compatible
test is invalid now, but would you prefer to remove it in a separate PR?
Test is no longer valid, and has been superseded by newly added tests
Apologies! I overlooked that bit of feedback. I agree, pushed a new commit to remove that test. |
Update cl_khr_command_buffer tests to reflect changes from KhronosGroup/OpenCL-Docs#1292
CL_DEVICE_COMMAND_BUFFER_SUPPORTED_QUEUE_PROPERTIES_KHR
from command-buffer creation to enqueue.CL_DEVICE_COMMAND_BUFFER_REQUIRED_QUEUE_PROPERTIES_KHR
from command-buffer creation to enqueue.CL_INVALID_DEVICE
on command-buffer enqueue for new error condition in spec. Although it requires a context to be contain more than 1 device, which I'm not sure if possible in current test framework.