You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tests/test_explicit_comms.py::test_dataframe_shuffle[True-tcp-cudf-1] cub/detail/detect_cuda_runtime.cuh(39): warning: cuda_runtime_api.h: [jitify] File not found
../util_type.cuh(42): warning: cuda.h: [jitify] File not found
cupy_jitify_exercise(10): warning: cooperative_groups.h: [jitify] File not found
cupy_jitify_exercise(11): warning: cooperative_groups/memcpy_async.h: [jitify] File not found
PASSED
It looks like this may be related to how CuPy uses CUB. Though it could easily be something else
Note: The test does pass. However the warning looks odd. Like something is misconfigured
The text was updated successfully, but these errors were encountered:
The noise should be suppressed by cupy/cupy#8235 and will be available starting CuPy v13.1.0. Question: Is this something that dask-cuda CI can help validate?
We can do a human validation when 13.1.0 is out, we don't make any automatic warning validation because several exist from Dask, which are also not suppressed to support debugging when something goes wrong.
Am seeing the following warning on CI
It looks like this may be related to how CuPy uses CUB. Though it could easily be something else
Note: The test does pass. However the warning looks odd. Like something is misconfigured
The text was updated successfully, but these errors were encountered: