Skip to content
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

CUDA initialization error in proxify_device_objects.py #491

Closed
pentschev opened this issue Jan 11, 2021 · 0 comments · Fixed by #492
Closed

CUDA initialization error in proxify_device_objects.py #491

pentschev opened this issue Jan 11, 2021 · 0 comments · Fixed by #492

Comments

@pentschev
Copy link
Member

Latest nightly tests failed due to CUDA initialization error, which seems to be rooted at

import cudf._lib.table
. I believe what's happening is that this is an import in the global level where dask-cuda can't ensure the CUDA context has already been created, in turn leaving that task then to cuDF.

@madsbk could you check if it's possible to move that import from the global level to a local one, in such a way as to prevent cudf from ever being imported before dask-cuda has had a chance to initialize the CUDA context? I took a quick look but it seems that this is an indirect dependency and I wasn't sure how to fix it without risking breaking something else.

@rapids-bot rapids-bot bot closed this as completed in #492 Jan 12, 2021
rapids-bot bot pushed a commit that referenced this issue Jan 12, 2021
Fixes #491 by moving dispatch of cudf objects within a `register_lazy("cudf")`.

Authors:
  - Mads R. B. Kristensen <[email protected]>

Approvers:
  - Peter Andreas Entschev (@pentschev)

URL: #492
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant