-
Notifications
You must be signed in to change notification settings - Fork 94
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
Error serializing CuPy==12.0.0 array #1174
Comments
The tests are run with warnings as errors. In cupy 12, So this distributed patch fixes things:
|
Thanks @wence- , that fixes things. However, we're still pinning to |
I opened #1175 to workaround the issue for now. |
As discussed in #1174, we must workaround test failures until Distributed can be unpinned. Authors: - Peter Andreas Entschev (https://github.com/pentschev) Approvers: - Lawrence Mitchell (https://github.com/wence-) URL: #1175
Now that Dask & Distributed 2023.5.1 are out (and have the fix). What are the next steps here? |
Closes #1174 Authors: - Peter Andreas Entschev (https://github.com/pentschev) Approvers: - Mads R. B. Kristensen (https://github.com/madsbk) - GALI PREM SAGAR (https://github.com/galipremsagar) URL: #1191
With the recent change of cuDF to require CuPy 12 a new issue has shown up in serialization tests, it doesn't occur with
cupy=11.6.0
and it passes after the first attempt to serialize a CuPy array in the same process. The following is a workaround for the tests:However, only the first parametrized test fails even without the above with all further instances passing. This hints at some change on how CuPy loads and Dask sees that, probably the registration of CuPy serializer only happens during the first serialization attempt.
The text was updated successfully, but these errors were encountered: