https://github.com/rapidsai/cugraph/pull/4509 proposed a stricter pattern for passing a pylibcugraph wheel from the wheel-build-cpp job that produced it into the wheel-build-python job wanting to use it (as a build dependency of cugraph). This change improves the likelihood that issues with the pylibcugraph wheels will be caught in CI.
This proposes porting that change here, so that when CI is set up in this repo, it'll also benefit from that strictness.
BradReesWork
commented
1 month ago
Description
Contributes to https://github.com/rapidsai/build-planning/issues/69 Contributes to https://github.com/rapidsai/build-planning/issues/33
Similar to https://github.com/rapidsai/cugraph-gnn/pull/7
https://github.com/rapidsai/cugraph/pull/4509 proposed a stricter pattern for passing a
pylibcugraphwheel from thewheel-build-cppjob that produced it into thewheel-build-pythonjob wanting to use it (as a build dependency ofcugraph). This change improves the likelihood that issues with thepylibcugraphwheels will be caught in CI.This proposes porting that change here, so that when CI is set up in this repo, it'll also benefit from that strictness.