-
Notifications
You must be signed in to change notification settings - Fork 69
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
github/workflows/cibuildwheel.yml: Add ubuntu aarch64 #196
Conversation
Looks like something went wrong with the runner, but it's not clear to me what the issue is. |
Also the runner seems to be caught in an infinite loop due to the error. Can you cancel the run manually? Ill have a look later |
Poking at this a bit, I'm not sure where the issue is. The error is from running an image that is not compatible with the platform, but it is not clear if this is a Github issue or a cibuildwheel issue. It could be the latter. Maybe try what's recommended here? |
Yes, the docker/setup-qemu-action is needed if one wants to build without setting things up properly for cross |
Unfortunately, Linux ARM runners are still in private beta so that will be the way to go. I am a bit confused that macos can build for arm on amd64, but linux cannot. I will implement the recommended qemu setup. |
Actually, MacOS can't do this either. |
Looks like two issues:
|
The attempted upgrade of the upload-artifact action here causes this. Changes like this are best not mixed in with the proposed changes for the purpose of this PR. upload-artifact v4 is not compatible with our use of the action. |
Hi everyone, yes the upload/download artifact version bumping is on me. However this needs to be addressed as well as the current used version is deprecated. Can / Should be addressed in another PR that is true. However the regarding the actual error for ubuntu aarch64 I think the error lies in the Line 13 in efe4314
In contrast to the builds for other os/archs it does not even start compiling. However, I am not that deep into that setup. |
Coincidentally, we just ran into this very same thing in a Cbc conda build on the same architecture. It seems our |
I would try this. |
I reverted my changes regarding the action version bump to get rid of the failing pipelines for the other architectures. However, it seems like you fix did not resolve the missing library in the last run: https://github.com/coin-or/CyLP/actions/runs/8880693060/job/24381324439 |
I should have done this before now, but I finally just tried building on a Raspberry Pi and it works fine. So I guess maybe this is just back to where we started, something is going wrong because we are not actually on an ARM runner. I have to admit that I don't really have a good understanding of what's going on here. I just set up one final try, using the build platform specification that my Raspberry Pi reports when I configure there. We'll see. |
Well, OK, that seems to have worked! |
Something's weird. All the builds seem to be working, but I hard-coded the build specification to be |
For whatever reason it also took a very long time to build all of the wheels. Maybe due to the virtualisation layer. |
It seems that the environment variable I'm a bit out of my depth here. I got the building of wheels working. If we can just get the environment variables set up properly inside |
6681203
to
9bd324b
Compare
@tkralphs Here's something that seems to work. |
The failure in integration testing with CVXPY was already present in master and is being resolved in #200 so I will go ahead and merge this. |
Build a wheel for linux on arm to enable e.g. dockerized usage on Apple Silicon an SBCs.
closes #158