-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Rebuild cuda118, cuda1120, and protobuf #195
Rebuild cuda118, cuda1120, and protobuf #195
Conversation
…nda-forge-pinning 2023.10.11.05.05.48
The transition to CUDA 12 SDK includes new packages for all CUDA libraries and build tools. Notably, the cudatoolkit package no longer exists, and packages should depend directly on the specific CUDA libraries (libcublas, libcusolver, etc) as needed. For an in-depth overview of the changes and to report problems [see this issue]( conda-forge/conda-forge.github.io#1963 ). Please feel free to raise any issues encountered there. Thank you! 🙏
…nda-forge-pinning 2023.10.11.19.37.54
…nda-forge-pinning 2023.10.23.08.51.53
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.10.23.08.51.53
These ones were running, but they were timed out: [5220/5707] Building CUDA object caffe2/CMakeFiles/torch_cuda.dir/__/aten/src/ATen/native/cuda/ForeachUnaryOp.cu.o
[5221/5707] Building CUDA object caffe2/CMakeFiles/torch_cuda.dir/__/aten/src/ATen/native/cuda/IGammaKernel.cu.o
[5222/5707] Building CUDA object caffe2/CMakeFiles/torch_cuda.dir/__/aten/src/ATen/native/cuda/Im2Col.cu.o
[5223/5707] Building CUDA object caffe2/CMakeFiles/torch_cuda.dir/__/aten/src/ATen/native/cuda/GridSampler.cu.o
##[error]The operation was canceled.
Finishing: Run docker build They just take really really long it seems. Not sure what can be done in order to reduce this time. |
I've always been building cuda locally. the fat binaries are just really slow to compile. |
I can try to start building this locally and see where it goes. I am not overly enthusiastic to build out 3 cuda versions (11.2, 11.8, and 12.0)..... |
I did not know that was an option hehe. I know how to build locally, but I assume the results are not something I can somehow upload here myself?
I understand it is a hassle, but torch is a really big package and I believe it is worth to provide these options. It is true though that minor CUDA versions are supposed to be compatible amongst them, but even in that case I would assume CUDA 11.8 provides some kind of performance enhancement with respect 11.2. |
See https://github.com/conda-forge/cfep/blob/main/cfep-03.md is 11.8 useful if we provide 12.0? It just really is ALOT of package data (storage) and compilation time. |
@RaulPPelaez were you able to get Cuda 12.0 to also compile? if so do you want to add it to this merge request and I can trigger a rebuild. |
Yeah we need to figure out a way to automate builds |
Those also timed out, the PR for CUDA 12 #193 should also be compatible with CUDA 11.8. |
@conda-forge-admin, please rerender |
…nda-forge-pinning 2023.10.30.17.31.54
Think what Mark is asking is if you have tried building locally (and if so whether those builds completed) Guessing most build errors occur early (like those seen previously: #193 (comment) ) Though there are some errors that might not show up until the linking stage Another question would be whether we see issues during testing (not sure what testing is done for the CUDA packages) |
I have the following done canaries completed.
That said, i'm wondering if for the sake of conda-forge's storage quote, if i shoul dcancel (now that I have one build of 11.2, 11.8 and 12.0 complete) cancel these builds and work to integrate #197 |
@h-vetinari do you have a sense of how #197 should factor in here? |
If it can be integrated, all the better! If not, it's not the end of the world, but should then go into the next build. With pytorch, the recent protobuf bumps seemed to go pretty smoothly though (from what I can tell, esp. compared to TF). |
they work. builds take a full day. restarting them now with protobuf migration |
…nda-forge-pinning 2023.11.02.10.11.59
log files |
Hi @hmaarrfk - have these builds actually been uploaded to the conda-forge channel? I might be blind seeing only the cpu builds. |
Background: I’m trying to figure out why conda-forge/pytorch_scatter-feedstock#55 can’t find solve the environment |
lol, maybe not.... I might just upload the next ones if that is ok? |
Meaning with the changes from PR ( #199 )? |
yes. I mean, i'm really not excited about them either, but they are complete.... |
Yeah that seems better from a user standpoint (recent version + Python 3.12) |
Ohhhh. i found the builds: https://anaconda.org/mark.harfouche/pytorch/files Just copied them over. |
Thanks Mark! 🙏 |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)Continuing #191 I added the necessary CUDA arch flags to build_pytorch.sh.