-
Notifications
You must be signed in to change notification settings - Fork 160
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
GPU tests failing (and taking a long time to run) #1357
Comments
Diff between environments: https://www.diffchecker.com/VUIKrubT/ Interestingly, only the build number for cupy and cupy-core are different. |
We've changed how cuda is installed and pinned cuda to 11.8, which was released in 2022. Things still seem to fail with the new installation method and cuda 12.3 and 12.2. I've merged the change to use 11.8 (plus a timeout and better version reporting) as a temporary fix for now. |
Please remove the toplevel .ci directory that holds one file. That file can live in .github. |
That directory will hold more files with the minimum version test job |
OK, but currently, that PR calls the directory |
@flying-sheep #1363 does that |
Awesome! Also thanks for helping fix this! |
The GPU tests seem to be failing, and taking at ~1.5 hours to do so, which is a little expensive
It looks like this was triggered when #1354 was merged, but I doubt this is the cause. I suspect it has to do with CUDA versions
Rapids single cell's tests aren't failing, but also has some slight different libraries installed. Includes:
libcublas
andpython
TODO:
cc: @flying-sheep @Intron7
Failure messages look like:
The text was updated successfully, but these errors were encountered: