CI: Enable arm64 runners
- Changes the way we pass repositories and versions/tags/branches so that we can use a single input for each pair, e.g.
graalvm/mandrel:graal/masterwhich is<repo>:<version> - Adds new
osinput to allow us to choseubuntu-24.04-armand macos at some point in the future. - Introduces a new weekly build on AArch64
Closes #823
Note: CI runs are expected to fail due to https://github.com/oracle/graal/pull/10858 not being merged yet.
Is there a GHA run with this?
Only for AArch64 https://github.com/zakkak/mandrel/actions/runs/13905609233 with a build of https://github.com/oracle/graal/pull/10858 which fails due to https://github.com/oracle/graal/pull/10856 not being present in https://github.com/oracle/graal/pull/10858
Once graal master gets in shape I plan to do a more complete run.
Scheduled a nightly and a weekly build on my repo for testing:
- https://github.com/zakkak/mandrel/actions/runs/14080588191
- https://github.com/zakkak/mandrel/actions/runs/14080588301
The pipelines look good as in "they run as expected". It seems we have some things to fix in the tests on AArch64, which I suggest doing separately.
@jerboaa WDYT? Merging this is going to create some (weekly) noise in https://github.com/graalvm/mandrel/issues/830.
The pipelines look good as in "they run as expected". It seems we have some things to fix in the tests on AArch64, which I suggest doing separately.
@jerboaa WDYT? Merging this is going to create some (weekly) noise in #830.
Most of the tests fail because of no Aarch64 image available needed for the tests. Most notably mssql, db2, oracle and ryuk containers.
Perhaps there is no point in including them when there are no images available to test? Should we get inclusions/exclusions for them added for Aarch64 before we merge?
Should we get inclusions/exclusions for them added for
Aarch64before we merge?
I was thinking what would be the best way to achieve this and I lean towards adding an extra field in https://github.com/quarkusio/quarkus/blob/main/.github/native-tests.json to indicate the "supported" architectures as this is expected to be useful if/when Quarkus enables AArch64 testing as well. I will start a discussion on the Quarkus repository.
Update: Discussion link https://github.com/quarkusio/quarkus/discussions/47084
Yes, this really is a quarkus test compatibility issue which would be visible in quarkus too. Best fixed there (in terms of test exclusions).
This PR appears to be stale because it has been open 30 days with no activity. This PR will be closed in 7 days unless Stale label is removed, a new comment is made, or not-Stale label is added.