Description
#43 improved support for pure-Python packages in RAPIDS. That included publishing all the pure-Python conda packages from conda-python-build jobs as their own artifact, like this:
image: cudf build job (link)
@mroeschke recently discovered a case where some cudf CI jobs were incorrectly pulling nightlies of dask-cudf (a pure-Python package) instead of the just-built-in-CI artifacts (rapidsai/cudf#21873), because the newly-named artifacts like cudf_conda_python_noarch_cu13 weren't getting downloaded in test jobs.
We should look through all of RAPIDS and ensure there aren't more cases like that.
Benefits of this work
- ensures that CI artifacts are used in CI, so bugs can be caught before PRs are merged
Acceptance Criteria
- every RAPIDS repo using
noarch packages is correctly pulling them into CI jobs that need them
Approach
Look through all the repos for those publishing noarch packages.
Add a task list here, open PRs fixing this with changes similar to rapidsai/cudf#21873
Here are all of the repos tracked building noarch packages as per #43
Additional repos with noarch packages (from https://github.com/search?q=org%3Arapidsai%20build_python_noarch.sh&type=code) (non-exhaustive search)
Additional checks
Walked through all instances of PYTHON_CHANNEL=, PYTHON_NOARCH_CHANNEL=, and *_WHEELHOUSE=
(https://github.com/search?q=org%3Arapidsai+%28PYTHON_CHANNEL%3D+OR+PYTHON_NOARCH_CHANNEL%3D+OR+_WHEELHOUSE%3D%29&type=code)
Notes
N/A
Description
#43 improved support for pure-Python packages in RAPIDS. That included publishing all the pure-Python conda packages from
conda-python-buildjobs as their own artifact, like this:image:
cudfbuild job (link)@mroeschke recently discovered a case where some
cudfCI jobs were incorrectly pulling nightlies ofdask-cudf(a pure-Python package) instead of the just-built-in-CI artifacts (rapidsai/cudf#21873), because the newly-named artifacts likecudf_conda_python_noarch_cu13weren't getting downloaded in test jobs.We should look through all of RAPIDS and ensure there aren't more cases like that.
Benefits of this work
Acceptance Criteria
noarchpackages is correctly pulling them into CI jobs that need themApproach
Look through all the repos for those publishing noarch packages.
Add a task list here, open PRs fixing this with changes similar to rapidsai/cudf#21873
Here are all of the repos tracked building
noarchpackages as per #43cuxfilter(scanned through all script files inci/and all usage ofrapids-download-from-githubare set to downloadnoarchbuildsdask-cuda(all downloads are correct)integration(n/a there are no intra-CI job artifact downloads)cudf(n/a handled upstream already)distributed-ucxx(conda recipe includes limited API and noarch builds all dumped into the same github artifact, that artifact is used in all conda testing. Wheel tests download the pure wheel)nx-cugraph(all downloads are correct)rapids-cli(all downloads are correct)Additional repos with
noarchpackages (from https://github.com/search?q=org%3Arapidsai%20build_python_noarch.sh&type=code) (non-exhaustive search)cugraph-gnn(all downloads are correct)Additional checks
Walked through all instances of
PYTHON_CHANNEL=,PYTHON_NOARCH_CHANNEL=, and*_WHEELHOUSE=(https://github.com/search?q=org%3Arapidsai+%28PYTHON_CHANNEL%3D+OR+PYTHON_NOARCH_CHANNEL%3D+OR+_WHEELHOUSE%3D%29&type=code)
Notes
N/A