-
-
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
Segfault when importing sklearn as well, osx-arm64 #260
Comments
The referenced issue ( pytorch/pytorch#132372 (comment) ) points to a user recreating the bug with "anaconda's default channel". We do not use "anaconda default channel" packages. If you can recreate with conda-forge only channel: please provide all the requested outputs from the issue template. they are critical when troubleshooting this.
then we can start to investigate. |
I also worked on a similar issue 2 months ago so getting the full output from you would really help troubleshoot things. |
yes, can recreate with c-f channel. will provide more info shortly. |
Here's the full output. It affects your v2.3.0 but not v2.4.0. In any case, I thought it would be useful to give you a heads-up about the
|
Thank you for the detailed installation and recreation. So from your experiments I can see that:
Can you try to see if
recreates things with pytorch 2.3.0 build 0. I think I hit this issue with: #243 We fixed it in 2.3.1 build 1 #244 I'm honestly not sure how far back to mark the pytorch M1 builds as broken. If you do the investigation, all with the conda-forge channel channel only, and show your work, I can try to merge in a PR that you make I unfortunately do not have an OSX arm machine, so it isn't easy for me to test. |
ok, cool. I can do this if you feel it's useful to your users? I maintain the pytorch recipe at anaconda, so this wouldn't be work that benefits me directly - I just thought making you aware of it might be helpful. But I'm happy to do it if you feel it's valuable. If it's low-priority and it's just making more work for you then no worries. Let me know :) |
And in general, let me know to what extent collaboration would be welcome |
its not low priority as much as "I can't really test it".
it is, but it might not be worth your time.
Generally speaking, i miss the days where the recipes were similar between conda-forge and anaconda. sharing ideas was much simpler. However, with things diverging, i'm not sure the extent that it is possible. Where is your pytorch recipe stored today? My general understanding was that collaboration was still happening on the I'm open to adding such shims. We have been having trouble with the aarch64 builds and that has been weighing me down. Help there would be greatly appreciated! See #256 |
Our recipe is here. It diverges a fair amount but there's some stuff in common too (I want to pull across the single building of libtorch stuff). |
@hmaarrfk what was the aarch64 issue you were having specifically? I couldn't really tell from a glance over the issue. Are you still having them? |
""PyTorch was compiled without NumPy support" error when running on Linux aarch64 + CUDA (on NVIDIA GH200) using the conda-forge build of PyTorch 2.4.0." |
Thanks. We heard about pytorch dropping their conda package builds. How's the support for win and triton at the moment? as I understand you don't have either, we're keen to help avoid losing users from the conda ecosystem, let me know what the status is there please. I've also seen the open PR for v2.5.0 so will have a look and see if I can debug anything. |
You can find a list of issues #273 I've tagged them all. I mean its all volunteer led. Comment on the appriopriate one, make a PR if you want to see it improve. So help where you can. To companies that are interested in windows support, I simply suggest volunteering to build things. It goes a long way. |
Oh, the conda-forge CI can't handle the pytorch build for windows? hmm ok. |
Good to know |
Solution to issue cannot be found in the documentation.
Issue
This issue affects the conda-forge version too.
The solution is
export PACKAGE_TYPE="conda"
in the recipe. This was the change that introduced the bug. It puts an openmp into the site-packages directory and uses that one, if the above env variable isn't set.Some more info:
otool -L on the libraries to see what they’re linking against:
pytorch v2.2:
pytorch v.2.3:
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: