-
Notifications
You must be signed in to change notification settings - Fork 106
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
Helix-related builds failing for Python Wheels install of cryptography on ARM32 #359
Comments
@MattGal - Can you please take a look at this? |
Hrm, I suspect unintended fallout from the --extra-index-url changes I made recently, though weird it's just now showing up. How might I get some hardware to try this out on? |
For the most part Docker does a good job of supporting arm via QEMU. My suggestion is to try building in a Win 10 Linux Containers environment. |
@MattGal - Any progress on this? This is getting in the way of producing other images because they all get built in the same job. |
I was able to reproduce the problem, but no progress made. My sense is we should disable the DockerFiles used and pick this back up when we actually have a real need to regenerate them. I'll chat with @Chrisboh and get back to you. |
Ooops, too many distractions. Here's my plan:
I should be able to do these three things before EOD and get back to you. |
It is fixable, I didn't troll the internet enough the first time it happened to find the workarounds. The bug is pypa/wheel#367 . I am applying the suggested workaround and reenabling the images via PR now. |
PR merged. |
It's failing on this line of the Dockerfile:
dotnet-buildtools-prereqs-docker/src/debian/10/helix/arm32v7/Dockerfile
Line 36 in 560e5e7
This is failing on all Debian/Ubuntu ARM32 Helix Dockerfiles.
Here's the relevant part of the error output:
Attached is the log output:
log.txt
The text was updated successfully, but these errors were encountered: