python: publish linux-aarch64 wheels on native ARM runners - #201
Open
thellert wants to merge 1 commit into
Open
Conversation
This was referenced Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
linux-aarch64 wheels for the EPICS PVA stack
There is no
linux-aarch64wheel on PyPI forepicscorelibs,pvxslibsorp4p, at any interpreter. All three publishmacosx_11_0_universal2,manylinux2014_x86_64/manylinux_2_28_x86_64andwin_amd64only. So on arm64 Linuxpip install p4psource-builds all three and needs a C toolchain on the host. A container image can stage one; a bare-metal install cannot be assumed to have one.Three PRs, one per repo, adding the missing rows:
epicscorelibspvxslibsp4pThey need to merge in that order:
pvxslibsbuilds againstepicscorelibs, andp4pagainst both. Until the one above it has merged and published, each downstream PR's aarch64 jobs are expected to fail — see the note in each.Why now. epics-base/epicscorelibs#21 and #48 proposed this in 2023 using QEMU, and were closed unmerged in favour of waiting for ARM-based hosted runners. Those runners are now generally available and free on public repositories, which removes both objections raised in that discussion: the build is native rather than ~40 minutes emulated, and the unit tests run against a real kernel, so
qemu-usernot translatingIP_MULTICAST_ALL,SO_RXQ_OVFL,IP_MULTICAST_IFandIPV6_MULTICAST_IFis no longer a factor.The change, identical in all three:
runs-on: ${{ matrix.runner || 'ubuntu-latest' }}, following the existing${{ matrix.cy || 'Cython' }}idiom, so the x86_64 and native rows are untouched.manylinux2014_aarch64rows for cp39–cp313 andmanylinux_2_28_aarch64for cp314/cp314t, mirroring the x86_64 set, each withrunner: ubuntu-24.04-arm.ubuntu-24.04-armbuildslinux-aarch64natively. (epics-base/ci-scripts already builds that target, as a cross-compile.)podman5.8.4 is preinstalled onubuntu-24.04-arm, the same version as on the x64 image, so thepodman runstep is unchanged.mdavidsaver/ci-core-dumper@masteris anode24action and GitHub-provided runtimes are arm64-native, so it needs no change.matrix.ml, so nothing collides, andsrc: truestays on the x86_64 cp314 row only.This repo
Second in the chain. Continues #48, which was closed unmerged in Oct 2023 in favour of native runners.
Expect the aarch64 rows to fail on this PR until epics-base/epicscorelibs#56 merges and publishes. The existing download line already carries
--only-binary epicscorelibs, so with no aarch64 wheel availablepip downloadfails immediately with a resolver error naming it, rather than falling back to the sdist. That is the intended behaviour and it costs almost no runner time. A re-run once epicscorelibs publishes should be clean; every other row is unaffected.