-
Notifications
You must be signed in to change notification settings - Fork 544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Dask/Distributed version #3978
Update Dask/Distributed version #3978
Conversation
@gpucibot merge |
@ajschmidt8 @pentschev CI seems to be installing an older nightly of dask-cudf:
which probably is the reason we're getting these fails? |
Guessing this is relevant ( rapidsai/cugraph#1637 (comment) ) |
rerun tests |
1 similar comment
rerun tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the change
- dask>=2021.6.0 | ||
- distributed>=2021.6.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why change from installing from main? Since CI is installing from main, we should keep this so dev environments behave like CI (and mirror cudf https://github.com/rapidsai/cudf/blob/0a4e8a1c860518c9e30f5289dea07bd0879fb642/conda/environments/cudf_dev_cuda11.2.yml#L64)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's still done above. Peter is just setting a minimum version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I think what Dante was asking for is that the conda dev environment files install Dask/Distributed main to match the same as CI is running on. I did that in 80c340d now.
Failures seem legit to the changes that were introduced in Distributed 2021.6.0, for example: ValueError: Metadata inference failed in `len`.
You have supplied a custom function and Dask is unable to
determine the type of output that that function returns.
To resolve this please provide a meta= keyword.
The docstring of the Dask function you ran should have more information. I'm guessing cuML will require an update to adapt to the changes above, similar to what has been done in rapidsai/cudf#8426 . Also ccing @galipremsagar in case he has thoughts or could work on addressing those. Also FYI, I'll be on PTO for the next couple weeks, so maybe someone will need to take this over or ensure those issues are addressed on a different PR before merging this. |
Just looked at the errors, this bug is in |
That would be great, thanks @galipremsagar ! |
I've checked out |
rerun tests |
@gpucibot merge |
rerun tests |
4 similar comments
rerun tests |
rerun tests |
rerun tests |
rerun tests |
Codecov Report
@@ Coverage Diff @@
## branch-21.08 #3978 +/- ##
===============================================
Coverage ? 85.32%
===============================================
Files ? 230
Lines ? 18093
Branches ? 0
===============================================
Hits ? 15437
Misses ? 2656
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
rerun tests |
Authors: - Peter Andreas Entschev (https://github.com/pentschev) Approvers: - AJ Schmidt (https://github.com/ajschmidt8) - https://github.com/jakirkham - Dante Gama Dessavre (https://github.com/dantegd) URL: rapidsai#3978
No description provided.