Use new rapids-dask-dependency metapackage for managing dask versions
#1270
Conversation
galipremsagar
added
improvement
|
cc: @pentschev There seems a single pytest that has been consistently failing - would you be able to look into it? |
|
I want to see if rapidsai/ucxx#123 will resolve the issue. If it doesn't let's disable UCXX testing and reenable it in branch-24.02. To disable UCXX testing we will replace the line https://github.com/rapidsai/dask-cuda/blob/branch-23.12/ci/test_python.sh#L58 with: |
galipremsagar
removed
the
5 - DO NOT MERGE
|
/merge |
This time all jobs seems to have passed, but will be happy to add this in a separate PR if you say so |
|
I'm adding the skip in #1273, I've seen it fail a few times now. |
…ns (rapidsai#1270) Currently dask versions are pinned as part of every release cycle and then unpinned for the next development cycle across all of RAPIDS. This introduces a great deal of churn. To centralize the dependency, we have created a metapackage to manage the required dask version and this PR introduces that metapackage as a dependency of dask-cuda. xref: rapidsai/cudf#14364 Authors: - GALI PREM SAGAR (https://github.com/galipremsagar) Approvers: - Peter Andreas Entschev (https://github.com/pentschev) - Jake Awe (https://github.com/AyodeAwe) URL: rapidsai#1270
Currently dask versions are pinned as part of every release cycle and then unpinned for the next development cycle across all of RAPIDS. This introduces a great deal of churn. To centralize the dependency, we have created a metapackage to manage the required dask version and this PR introduces that metapackage as a dependency of dask-cuda.
xref: rapidsai/cudf#14364