Skip to content

wheels CI: test mix of cuda-toolkit version in CI #256

@jameslamb

Description

@jameslamb

Description

RAPIDS projects attempt to support a wide range of minor versions within each major CUDA version.

They should test that support in wheels CI by pinning to specific cuda-toolkit package versions.

Benefits of this work

  • improves test coverage of RAPIDS compatibility claims
  • reduces the risk of runtime issues with other projects that pin back to older-than-latest CTKs
  • side benefit: makes it easier for RAPIDS projects to add more lower-bound testing (say, of cupy or numpy) in the future
    • *(because this will be the first time some projects have used

Acceptance Criteria

  • RAPIDS wheels are tested against multiple versions of the cuda-toolkit metapackage per each supported major CTK version

Approach

Test in cuVS: rapidsai/cuvs#1855

We probably want something like pip constraints that constraint cuda-toolkit to whatever {major}.{minor} is set in the RAPIDS_CUDA_VERSION environment variable, similar to how cuda-version is set for conda environments:

  cuda_version:
    specific:
      - output_types: conda
        matrices:
          - matrix:
              cuda: "12.2"
            packages:
              - cuda-version=12.2

(rapidsai/cudf - dependencies.yaml)

Notes

A few things have all led up to this:

Metadata

Metadata

Assignees

Labels

improvementImproves an existing functionalitynon-breakingIntroduces a non-breaking change

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions