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
{{ message }}
Repository navigation
[ENH]: Pathfinder CI test case coverage improvements #1093
cuda.pathfinder is currently tested in CI for two CTK installation modes: a system CTK and one whose components are individually provided via wheels. Generally, pathfinder seems to be tested wherever cuda.bindings and cuda.core are tested.
Instead, cuda.pathfinder ought to have its own matrix of CI jobs that test the four installation modes that are supported: a system install, a wheel install, a conda install, and a local install of the ctk at a nonstandard directory the user points to via CUDA_HOME.
The solution might look like removing the pathfinder tests from the existing jobs and assigning a dedicated CI workflow to pathfinder that runs pathfinder tests across all the CTK installation modes. Existing testing coverage of cuda-core and cuda-bindings could be maintained if desired.
Activity
brandon-b-miller commentedon Oct 7, 2025
cc @rwgk
rwgk commentedon Oct 28, 2025
Test matrix:
rwgk commentedon Oct 28, 2025
Commands to set up environments:
rwgk commentedon Oct 28, 2025
Commands for testing:
For local-ctk testing:
CUDA_HOMEmust be set in the environment8 remaining items
rparolin commentedon May 29, 2026
@rwgk I'm going to close this ticket out given that we aren't working on it anymore. Feel free to re-open if you believe it was a mistake.
leofang commentedon May 29, 2026
I will take a stab at this.