-
Notifications
You must be signed in to change notification settings - Fork 513
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
Build for linux/arm64 fails #3622
Comments
I'm not sure we should assume the build is broken after just [20m] 40m; ARM builds on Github often run very slowly - i've seen PyMuPDF ARM builds take several hours. I think Github may be using an emulator. Suggest you let it run until Github times out (6h i think). |
My Arm build won't run any version greater than 1.24.5. What do you want us to test so we can give you feedback. I had to update our requirements.txt file to make sure it only uses 1.24.5 |
I am running into the same issue on an Mac M1 arm build (local) |
@julian-smith-artifex-com what information are you waiting for? I'm happy to do whatever you need to help resolve this. I am stuck at version 1.24.5 until this is resolved. All our docker containers run on an arm server. |
The first line of the log at https://github.com/comfuture/glados/actions/runs/9674016697/job/26688926160#step:8:848 is:
The end of the log is:
So it looks like the Github workflow was manually cancelled about 20 min after it started. So i'd like you to run the build again and leave it to run to completion without cancelling it. [Github will kill it if it hasn't finished after 6 hours] I'm not familiar with |
I think this is independent of flit. I have local poetry as the built system and on version 1.24.5 my example docker image is building in 20 secconds with flag --no-cache while with the 1.24.9 it is stuck forever with preparing metadata as shown in the log. pyproject.toml
poetry.lock
Dockerfile
|
Linux/aarch64 wheels were missing from pypi.org until a few days ago. So it's possible that pip or poetry or other Python packaging tools have been trying to build from source, which can take a long time (e.g. hours). The wheels are now available on pypi.org, so please retry, and report back here with the results. |
That makes sense it still took 160s instead of 20s with prior version(1.24.5), which is an 8x increase, but it completed the build and worked on my local machine. for my use case this is fine, thank you |
Thanks for the update, I'll close this issue. |
Description of the bug
Problem
Installing PyMuPDF on linux/arm64 fails while install dependencies on linux/arm64 docker build.
To make multiarch image, I've made a github workflow that builds the image for both amd64 and arm64. The build for amd64 is successful, but the build for arm64 stuck with the following error:
https://github.com/comfuture/glados/actions/runs/9674016697/job/26688926160#step:8:848
How to reproduce the bug
The project has files as follows:
pyproject.toml is as follows:
Dockerfile is as follows:
The workflow deploy.yaml is as follows:
Then push the project to the repository, and the workflow will be triggered.
PyMuPDF version
1.24.6
Operating system
Linux
Python version
3.11
The text was updated successfully, but these errors were encountered: