KhronosGroup / KhronosGroup/OpenCL-CTS
SVM enqueue_api tests with not so random fill patterns
- Dominant language
- C++
- Stars
- 232
- Forks
- 235
- Avg merge
- 8d 7h
- Merged PRs (30d)
- 18
Description
I was debugging those tests and noticed that only the first 4 bytes of the test patterns are actually random, the remaining bytes are always `[f8, f7, f7, f7]`
e.g.:
```
[dd, c8, e9, 5d, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7]
[54, 31, 57, 2e, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7, f8, f7, f7, f7]
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the SVM enqueue_api tests and inspect how their test patterns are generated. Confirm why only the first four bytes vary, make the remaining bytes non-constant, and verify that the tests still pass with genuinely varied patterns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100