Migrate all suites to the new test registration framework
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- testing-qa
Research direction
Start by reviewing PR 2151, which introduced the centralised test registration framework, and compare it with the remaining d3d11, gl, gles, and spir suites. The work is complete when each remaining suite is migrated and its status is reflected in this issue.
Written by the indexing model from the issue text.
Description
https://github.com/KhronosGroup/OpenCL-CTS/pull/2151 introduced a new centralised test registration framework. We should migrate all the test suites to this framework to enable further centralised improvements of the test framework.
Here is a list of all the suites with the current status:
- allocations (https://github.com/KhronosGroup/OpenCL-CTS/pull/2191)
- api (https://github.com/KhronosGroup/OpenCL-CTS/pull/2196)
- atomics (https://github.com/KhronosGroup/OpenCL-CTS/pull/2189)
- basic (https://github.com/KhronosGroup/OpenCL-CTS/pull/2316)
- buffers (https://github.com/KhronosGroup/OpenCL-CTS/pull/2315)
- c11_atomics (https://github.com/KhronosGroup/OpenCL-CTS/pull/2318)
- commonfns (https://github.com/KhronosGroup/OpenCL-CTS/pull/2197)
- compiler (https://github.com/KhronosGroup/OpenCL-CTS/pull/2319)
- computeinfo (https://github.com/KhronosGroup/OpenCL-CTS/pull/2320)
- contractions (https://github.com/KhronosGroup/OpenCL-CTS/pull/2321)
- conversions (https://github.com/KhronosGroup/OpenCL-CTS/pull/2322)
- d3d10 (https://github.com/KhronosGroup/OpenCL-CTS/pull/2662)
- d3d11 (https://github.com/KhronosGroup/OpenCL-CTS/pull/2724)
- device_execution (https://github.com/KhronosGroup/OpenCL-CTS/pull/2323)
- device_partition (https://github.com/KhronosGroup/OpenCL-CTS/pull/2301)
- device_timer (https://github.com/KhronosGroup/OpenCL-CTS/pull/2151)
- events (https://github.com/KhronosGroup/OpenCL-CTS/pull/2324)
- extensions (https://github.com/KhronosGroup/OpenCL-CTS/pull/2334)
- generic_address_space (https://github.com/KhronosGroup/OpenCL-CTS/pull/2333)
- geometrics (https://github.com/KhronosGroup/OpenCL-CTS/pull/2335)
- gl
- gles
- half (https://github.com/KhronosGroup/OpenCL-CTS/pull/2329)
- images (https://github.com/KhronosGroup/OpenCL-CTS/pull/2328)
- integer_ops (https://github.com/KhronosGroup/OpenCL-CTS/pull/2332)
- math_brute_force (https://github.com/KhronosGroup/OpenCL-CTS/pull/2327)
- mem_host_flags (https://github.com/KhronosGroup/OpenCL-CTS/pull/2314)
- multiple_device_context (https://github.com/KhronosGroup/OpenCL-CTS/pull/2325)
- non_uniform_work_group (https://github.com/KhronosGroup/OpenCL-CTS/pull/2317)
- pipes (https://github.com/KhronosGroup/OpenCL-CTS/pull/2302)
- printf (https://github.com/KhronosGroup/OpenCL-CTS/pull/2311)
- profiling (https://github.com/KhronosGroup/OpenCL-CTS/pull/2187)
- relationals (https://github.com/KhronosGroup/OpenCL-CTS/pull/2312)
- select (https://github.com/KhronosGroup/OpenCL-CTS/pull/2198)
- spir
- spirv_new (https://github.com/KhronosGroup/OpenCL-CTS/pull/2151)
- subgroups (https://github.com/KhronosGroup/OpenCL-CTS/pull/2313)
- SVM (https://github.com/KhronosGroup/OpenCL-CTS/pull/2168)
- thread_dimensions (https://github.com/KhronosGroup/OpenCL-CTS/pull/2309)
- vectors (https://github.com/KhronosGroup/OpenCL-CTS/pull/2190)
- vulkan (https://github.com/KhronosGroup/OpenCL-CTS/pull/2278)
- workgroups (https://github.com/KhronosGroup/OpenCL-CTS/pull/2308)
- Dominant language
- C++
- Stars
- 234
- Forks
- 240
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from KhronosGroup/OpenCL-CTS
-
cognizant-backlog
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
KhronosGroup/OpenCL-CTS#2882 · 1 comment ·
Maintainers usually reply within 1 day
-
cl_khr_command_buffer: negative_enqueue_inconsistent_device expects CL_INCOMPATIBLE_COMMAND_QUEUE_KHR instead of CL_INVALID_DEVICEPossibly taken @kpet claimed this 11 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
KhronosGroup/OpenCL-CTS#2872 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
test_compiler: feature macros for cl_ext_float_atomics are not testedPossibly taken @shajder claimed this 10 days ago. Opencognizant-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/OpenCL-CTS#2818 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
KhronosGroup/OpenCL-CTS#2699 · 1 comment ·
Maintainers usually reply within 1 day
-
cleanup/refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
KhronosGroup/OpenCL-CTS#2057 ·
Maintainers usually reply within 1 day
All issues in KhronosGroup/OpenCL-CTS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
useless statementOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
grizzlypeak3d/DJV#962 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day