Repository navigation
[ENH]: Pathfinder CI test case coverage improvements #1093
Description
Activity
cc @rwgk
Test matrix:
- 1-site-packages
- 1-linux-64
- cu12
- cu13
- 2-linux-aarch64
- cu12
- cu13
- 3-win-64
- cu12
- cu13
- 1-linux-64
- 2-local-ctk
- 1-linux-64
- cu12
- cu13
- 2-linux-aarch64
- cu12
- cu13
- 3-win-64
- cu12
- cu13
- 1-linux-64
- 3-conda-ctk
- 1-linux-64
- cu12
- cu13
- 2-linux-aarch64
- cu12
- cu13
- 3-win-64
- cu12
- cu13
- 1-linux-64
for pkgsys in ("1-site-packages", "2-local-ctk", "3-conda-ctk"): print(f"* {pkgsys}") for arch in ("1-linux-64", "2-linux-aarch64", "3-win-64"): print(f" * {arch}") for cumajor in ("12", "13"): print(f" * cu{cumajor}")
- 1-site-packages
Commands to set up environments:
- site-packages (identical on all platforms)
cd cuda_pathfinder/ pip install -v -e . --group test-cu13pip install -v -e . --group test-cu12
- local-ctk
cuda_13.0.2_580.95.05_linux.run cuda_13.0.2_580.95.05_linux_sbsa.run cuda_13.0.2_windows.execuda_12.9.1_575.57.08_linux.run cuda_12.9.1_575.57.08_linux_sbsa.run cuda_12.9.1_576.57_windows.execd cuda_pathfinder/ pip install -v -e . --group test
- conda-ctk
toolshed/conda_create_for_pathfinder_testing.sh 13.0.2toolshed/conda_create_for_pathfinder_testing.sh 12.9.1toolshed/conda_create_for_pathfinder_testing.ps1 13.0.2toolshed/conda_create_for_pathfinder_testing.ps1 12.9.1cd cuda_pathfinder/ pip install -v -e . --group testCommands for testing:
export CUDA_PATHFINDER_TEST_LOAD_NVIDIA_DYNAMIC_LIB_STRICTNESS=all_must_work export CUDA_PATHFINDER_TEST_FIND_NVIDIA_HEADERS_STRICTNESS=all_must_work cd cuda_pathfinder/ pytest -ra -s -v tests/$env:CUDA_PATHFINDER_TEST_LOAD_NVIDIA_DYNAMIC_LIB_STRICTNESS = "all_must_work" $env:CUDA_PATHFINDER_TEST_FIND_NVIDIA_HEADERS_STRICTNESS = "all_must_work" cd cuda_pathfinder\ pytest -ra -s -v tests\For local-ctk testing:
CUDA_HOMEmust be set in the environment4 remaining items
- changed the title
[-]Pathfinder CI test case coverage improvements[/-][+][ENH]: Pathfinder CI test case coverage improvements[/+]on Mar 4, 2026 @rwgk Are we still working on this?
Short answer: No
Not directly at least. I'm adding more mocks on the go while working on #1038 / #1977. When I'm done with that ("days, not weeks"), it'd make sense to make a pass cleaning up the pathfinder tests as a whole, but currently I don't think it needs to be a big project (like what I had in mind back in October).
I will take a stab at this.
cuda.pathfinderis 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 wherevercuda.bindingsandcuda.coreare tested.Instead,
cuda.pathfinderought 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 viaCUDA_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-coreandcuda-bindingscould be maintained if desired.