-
Notifications
You must be signed in to change notification settings - Fork 75
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
Force conda version of cutensor #765
Force conda version of cutensor #765
Conversation
@manopapad I was able to force conda's cutenosor. It is a little fragile, and currently it depends on the difference in the build string format between the packages. In any case, with cuda 11.8 there are errors you can see in this CI pipeline. Let me know what do you think about these errors, and if I should try to go back to cuda 11.5, |
@m3vaz Is there a better way to select cutensor from the conda forge channel over the one from nvidia? |
This actually fixes the 1-GPU failures. The other failures are expected, and will be handled by a different workaround. Thanks for taking care of this! |
I think the issue here is that the cutensor package on the nvidia conda channel is only compatible with CUDA 12, and there are no constraints on the packages to signal that the package is incompatible with the currently installed CTK conda package. As a matter of fact, there are no (recursive or otherwise) dependencies on a CTK package, or a runtime constraint on the driver version. There are also no build IDs, but I don't know if that matters.
|
btw we cannot not yet support cutensor's CUDA 12 flavor on conda-forge yet. Need to wait for the first wave of tasks outlined in conda-forge/staged-recipes#21382 done. |
Merging this for now, to make CI pass. We will have to fix this properly, before the Nvidia channel packages change their build IDs, breaking this workaround. |
FYI, when running with
|
No description provided.