processing / processing/libprocessing
[release.yml] linux aarch64 build
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 69
- Forks
- 14
- Avg merge
- 15d 22h
- Merged PRs (30d)
- 3
Description
There is a todo item in the release.yml for the linux aarch64 build. It actually does build, but we don't need to let it slow us down.
It takes 4.5 hours to build for it! That's so much.
I think this might have something to do with it having to use qemu in order to run an aarch64 container on an x86_64 runner.
We need to turn this back on, and it would be nice to make it fast.
My hunch is that we might be able to just put the linux-aarch64 build in its own step using an appropriate container? Does that exist?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in release.yml by locating the TODO for the Linux aarch64 build and review how its container and runner are configured. Compare that setup with the other release targets and investigate whether an appropriate native or dedicated container can avoid QEMU. Done means the aarch64 build is enabled without the current excessive delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100