Skip to content

Set up daily CI jobs to validate XGBoost against latest CCCL and RMM #232

@hcho3

Description

@hcho3

Currently, XGBoost is not being tested against latest CCCL and RMM. Breaking changes are not found until much later in the development cycle. For example: conda-forge/xgboost-feedstock#259 was blocked because XGBoost was found to be incompatible with CCCL 3.1. The particular incompatibility was due to an upstream bug (NVIDIA/cccl#6419). Had we found about this bug earlier, we could have addressed it sooner in the development cycle.

Proposal: Set a nightly CI job on the dmlc/xgboost repo to validate XGBoost against latest CCCL and RMM.

The CI job should be nightly so that it doesn't block pull requests.

For this effort to be successful, I or someone else should regularly monitor the status of the nightly CI.

Discussion: Which version of CCCL and RMM should we test with XGBoost?

  • Latest stable?
  • Latest nightly version?

Sometimes, nightly versions of RMM and CCCL may not be compatible with each other. Given their relative position in the software stack, I propose:

  • Use latest stable version of CCCL
  • Use nightly version of RMM

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions