Description
#782 added the first CUDA 13 builds here.
At that time, there weren't yet CUDA 13 XGBoost packages, and so some cuML notebooks failed to run.
We worked around that by just skipping cuML notebooks in CUDA 13 CI here:
#782 (comment)
Once there are XGBoost CUDA 13 packages and the rapids metapackage depends on them (tracked in rapidsai/integration#798), that testing should be restored here.
Benefits of this work
- improves release confidence
Acceptance Criteria
- cuML notebooks are testing in CUDA 13 CI here
Approach
Get rapids metapackage depending on CUDA 13 XGBoost packages:
Then revert the workarounds for cuML notebooks added in #782
Notes
N/A
Description
#782 added the first CUDA 13 builds here.
At that time, there weren't yet CUDA 13 XGBoost packages, and so some cuML notebooks failed to run.
We worked around that by just skipping cuML notebooks in CUDA 13 CI here:
#782 (comment)
Once there are XGBoost CUDA 13 packages and the
rapidsmetapackage depends on them (tracked in rapidsai/integration#798), that testing should be restored here.Benefits of this work
Acceptance Criteria
Approach
Get
rapidsmetapackage depending on CUDA 13 XGBoost packages:xgboost/rapids-xgboostforrapidspackages integration#798Then revert the workarounds for cuML notebooks added in #782
Notes
N/A