Investigate and document or fix all OpenCL CTS KNOWN_FAILUREs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- testing-qa
Research direction
Review the UUR_KNOWN_FAILURE_ON uses in the CTS and the unchecked entries listed for fixtures.h, urMemImageCreate.cpp, urKernelSetArgValue.cpp, and related files. Follow subtasks #2638 and #2644 first, then investigate the remaining FPGA, iGPU, and OpenCL failures. Done means each known failure has a linked issue or an explanation for why it is outside the project’s control.
Written by the indexing model from the issue text.
Description
All uses of the UUR_KNOWN_FAILURE_ON macro in the CTS should ideally be accompanied by a link to an issue, or, if the fail is due to something out of our control, an explanation as to why. This issue represents a quick collating of all the OpenCL KNOWN_FAILUREs, subtasks should be spun out to coordinate working on individual cases.
- FPGA emulator sampler fails
- fixtures.h:208 fixtures.h:333 urSamplerCreate.cpp:14 urKernelSetArgSampler.cpp
- #2633
- #2647
- igpu fails mem image size query in urMemGetInfo.cpp
- #2638
- fpga fails all (or at least most) tests in urMemImageCreate.cpp
- igpu fails InvalidSize test in urMemImageCreate.cpp
- suspect this is a known driver issue
- need pool support query to skip POOL enum in urUSMGetMemAllocInfo.cpp
- #2644
- igpu fail at urKernelSetArgValue.cpp:51
- probably just lack of validation like the MemImageCreate fail
- all CL devices fail urKernelGetSubGroupInfo.cpp
- maybe linked to urKernelGetGroupInfo fail?
- check why NUM_REGS being optional doesn't skip the test properly for CL in urKernelGetInfo.cpp
- Dominant language
- C++
- Stars
- 57
- Forks
- 120
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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 oneapi-src/unified-runtime
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
oneapi-src/unified-runtime#2848 · 1 comment ·
-
specification
Difficulty 4/5 3-5 days Newbie friendliness 25/100
oneapi-src/unified-runtime#2782 · 4 comments ·
-
bug level-zero
Difficulty 4/5 3-5 days Newbie friendliness 35/100
oneapi-src/unified-runtime#2742 · 2 comments ·
-
level-zero
Difficulty 4/5 3-5 days Newbie friendliness 45/100
oneapi-src/unified-runtime#2740 · 1 comment ·
-
conformance cuda
Difficulty 3/5 1-2 days Newbie friendliness 48/100
oneapi-src/unified-runtime#2720 ·
All issues in oneapi-src/unified-runtime
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·