kokkos / kokkos/kokkos-tutorials
Friction points for CI
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 388
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
Some pain points kept https://github.com/kokkos/kokkos-tutorials/pull/101 from being comprehensive:
-
virtualfunctionneeds a separate CUDA-enabled Kokkos build with RDC enabled - Not all exercises use CMake
- Not all exercises have the same structure (e.g. no
Begin/Solutionsubdirectories) - Some exercises hard-code specific execution spaces (purposefully or otherwise)
- Some exercises need additional libraries
- Kokkos Kernels (okay, slow-ish to build)
- Kokkos remote spaces
- Some exercises use Kokkos Kernels implementation details (testing utility functions)
- Some exercises use deprecated interfaces (tasking?)
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.
Research direction
Start by reviewing pull request 101 and the exercise build configurations, especially the virtualfunction exercise and the exercises that do not use CMake or share the same directory structure. Inventory the execution-space, library, Kokkos Kernels, remote-space, and deprecated-interface issues listed here. Done means the CI friction points are resolved or explicitly accounted for across the tutorials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100