CU_VERSION and CUDA_VERSION is confusing on Windows CI.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
🐛 Describe the bug
It's just a memo for developer to understand some code to get the cuda version.
In unittest_windows_cpu and cmake_windows_gpu
CU_VERSION is cpu, CUDA_VERION is empty.
In unitest_windows_gpu,
CU_VERSION is emtpy, CUDA_VERSION is MAJOR.MINOR (e.g. 10.2)
In cmake_windows_gpu
CU_VERSION is something like cu102, CUDA_VERSION is empty
Versions
It has existed for a long time.
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 reading the unittest_windows_cpu, unittest_windows_gpu, and cmake_windows_gpu Windows CI jobs and compare how CU_VERSION and CUDA_VERSION are set. Determine the intended distinction or consistent naming, then update the relevant CI documentation or configuration so the values are no longer confusing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system, ci-cd
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100