You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a CCCL maintainer, I would like to be able to test CCCL across a wide variety of use cases.
Currently, the matrix.yaml is the source of truth for all the environments that are tested in our CI.
Currently, this matrix is defined in such a way that it assumes you are always using nvcc + host compiler to do compilation of CUDA C++/C++ code.
However, there are a variety of additional use cases that don't fit this pattern. For example:
Testing with NVRTC where we only compile device code and don't need nvcc or a host compiler
Compiling host-only TUs for things like Thrust/libcu++ that are expected to work without nvcc
Compiling CUDA code with clang
Describe the solution you'd like
Extend the current matrix.yaml by nesting all of the current environments under a nvcc: field, and then add additional fields for the other kinds of jobs. For example:
Is this a duplicate?
Area
Infrastructure
Is your feature request related to a problem? Please describe.
As a CCCL maintainer, I would like to be able to test CCCL across a wide variety of use cases.
Currently, the
matrix.yaml
is the source of truth for all the environments that are tested in our CI.Currently, this matrix is defined in such a way that it assumes you are always using
nvcc
+ host compiler to do compilation of CUDA C++/C++ code.However, there are a variety of additional use cases that don't fit this pattern. For example:
Describe the solution you'd like
Extend the current
matrix.yaml
by nesting all of the current environments under anvcc:
field, and then add additional fields for the other kinds of jobs. For example:Tasks
The text was updated successfully, but these errors were encountered: