RAPIDS depends heavily on CuPy and does tests stable versions of CuPy when developing RAPIDS.
However there is currently limited testing of CuPy with RAPIDS during development. As a result, sometimes issues can crop up after a CuPy release that were not caught earlier.
Currently this is what exists:
To help prevent this, RAPIDS should adopt broader testing of CuPy nightlies or pre-releases. As cuML started this with pre-releases, this could provide a good initial template to build out more RAPIDS testing of CuPy pre-releases.
For CuPy nightlies testing, we would need nightly binaries from CuPy, which don't exist yet. This tracked in issue: cupy/cupy#9974
By doing this RAPIDS should be able to report upstream issues with CuPy during development before releases to ensure fewer issues show up after CuPy releases.
RAPIDS depends heavily on CuPy and does tests stable versions of CuPy when developing RAPIDS.
However there is currently limited testing of CuPy with RAPIDS during development. As a result, sometimes issues can crop up after a CuPy release that were not caught earlier.
Currently this is what exists:
To help prevent this, RAPIDS should adopt broader testing of CuPy nightlies or pre-releases. As cuML started this with pre-releases, this could provide a good initial template to build out more RAPIDS testing of CuPy pre-releases.
For CuPy nightlies testing, we would need nightly binaries from CuPy, which don't exist yet. This tracked in issue: cupy/cupy#9974
By doing this RAPIDS should be able to report upstream issues with CuPy during development before releases to ensure fewer issues show up after CuPy releases.