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
In all my attempts for test_cudf_device_spill() I have seen param0 (with "spills_to_disk": False,) always fail but param1 (with "spills_to_disk": True) suceeds sometimes.
Steps/Code to reproduce bug
Install the dask-cuda 0.9.1 and cudf 0.9.0 conda package which we have built for linux_ppc64le
Please let me know if some other information is required to get to the root cause of this issue. Thank you!
The text was updated successfully, but these errors were encountered:
ksangeek
changed the title
test_spill.py::test_cudf_device_spill fails in linux_ppc64le
[BUG] test_spill.py::test_cudf_device_spill fails in linux_ppc64le
Sep 30, 2019
Thanks for the report @ksangeek. This particular test has been pretty difficult to ensure limits are correct, and they seem to manifest differently for different systems.
We should eventually try to improve that test, but I'm not really sure how to do it today. Also I'd say that the issue is with the test rather than the actual functionality, and the passing CuPy tests help to ensure that (but doesn't eliminate the possibility of a bug).
Describe the bug
Executing dask-cuda 0.9.1
test_spill.py
test on a IBM AC922 (linux_ppc64le) fails fortest_cudf_device_spill()
-Pls note -
test_spill.py
succeed!test_cudf_device_spill()
I have seenparam0
(with"spills_to_disk": False,
) always fail butparam1
(with"spills_to_disk": True
) suceeds sometimes.Steps/Code to reproduce bug
0.9.1
and cudf0.9.0
conda package which we have built for linux_ppc64lev0.9.1
code of https://github.com/rapidsai/dask-cuda.gitdask_cuda/tests
pytest test_spill.py::test_cudf_device_spill
Expected behavior
The testcase should succeed!
Environment details
Additional context
I added some print statements in the test and see that this condition fails -
These were the values for
param0
andparam1
respectively when it failed -For the odd case when
param1
succeeded, these were the values -Patch of the testcase which I used to add the print -
Please let me know if some other information is required to get to the root cause of this issue. Thank you!
The text was updated successfully, but these errors were encountered: