tests/std: CUDA tests should try device-side code
Open
Nobody has claimed this yet.
test
- Dominant language
- C++
- Stars
- 11.1k
- Forks
- 1.7k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 22
Description
The bug introduced in #1336 slipped by testing because the tests only try to build host-side (CPU) code while the error shows up when building device-side code (GPU). We should try building device-side code as well to avoid this happening in the future (so far, I have found that the PR broke PyTorch, Blender, FFMPEG, OpenPose and the Intel Compiler)
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 in tests/std and review the regression described in #1336, focusing on how the current CUDA tests build host-side code. Add coverage for a device-side build and verify that the failure from #1336 is caught.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100