o5logon-opencl fails self-tests
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
o5logon-opencl has been failing or crashing more or less intermittently for some time, on most devices/drivers. With latest changes (merged yet or not) to autotune and self-tests, it seems to fail more often or every time. I have stared at it in the past and again in the last few days but can't find the problem.
Sometimes it's just a self-test failure such as FAILED (crypt_all(1) zero return). Sometimes it crashes, in various places (for example, in set_key when trying to send a partial batch to GPU).
Contributor 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.
Research direction
Start by reproducing the o5logon-opencl self-test failures across devices and drivers, then inspect the autotune and self-test changes and the set_key path that sends partial batches to the GPU. Done means the self-tests pass reliably without crashes in those paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100