Marcin Hajder

@bashbaug I guess it was already completed along with #2378. Please confirm it is [correct](https://github.com/KhronosGroup/OpenCL-CTS/blob/8701acfa90b5e95772782bbdfb1997a1623d43c1/test_conformance/api/test_zero_sized_enqueue.cpp#L101-L110) fix for the issue, thanks!

After reviewing CTS source code I identified below missing nevative coverage for clSetKernelArg: edit: work plan moved to issue description to align with github sub-tasks scheme

> Is this case sufficiently well-specified? I had nothing specific on my mind - just followed spec for clSetKernelArg. I conclude from your question this is not a real-life case,...

@kpet @bashbaug In my evaluation of test coverage for the `test_bufferreadwriterect` function, I'm assuming that by randomizing the argument values with equal probability, we're likely to cover all necessary scenarios...

@svenvh do you know if [the concern](https://github.com/KhronosGroup/OpenCL-CTS/blob/5b3518096ca7b82854daadb2b2fae704fe2d9cb5/test_conformance/math_brute_force/function_list.cpp#L400) behind `tgamma` precision is already sorted out ? Thanks

@niranjanjoshi121 just for clarification, is issue #1876 the same as this one ? Thanks > test_semaphores_import_export_fd requires cl_khr_external_sync_fd and hence should not be part of base cl_khr_semaphore tests @niranjanjoshi121 @bashbaug...

> These APIs have a slightly different pattern: they return an array of objects and/or the number of objects in the array. Indeed, pattern is not reflected exactly in mentioned...

close/open to retrigger CI

close/open to retrigger CI

> I don't think this test is doing the right thing. Please double-check the flow described in #1979... Right, I think I see the mistake, sorry for confusion. After correction...