There are several options to build for ARM using github workflows: hosted server , qemu and using macos-14 image.
1. Hosted server: dependency on an external server 2. qemu: extremely slow 3. macos14: Transparent usage compared to other run images, eg. ubuntu-latest, windows-latest. Con is that I am not sure if avro can be compiled on macos-latest (because of size constraints). There are macos-large and xlarge images, however those are not free. I have put together an example project which builds a simple C# project on Ubuntu 22.04 (x64), Windows 10 (x64), Darwin 21.6 (x64), Darwin 23.2 (arm64). It demonstrates a unified way to build and run a sample project on the 4 above images. Check the Run step output, which shows the OS and architecture info. https://github.com/zcsizmadia/test-arm64 https://github.com/zcsizmadia/test-arm64/actions https://github.com/zcsizmadia/test-arm64/actions/workflows/test-multi-os.yml Maybe something similar could be used for the avro build. Regards, Zoltan On Thu, Feb 1, 2024 at 7:33 AM Niels Basjes <ni...@basjes.nl> wrote: > Hi, > > I noticed that most of the build failures are currently related to the ARM > build system being flaky. > So we see that the Java build or the C# build has failed ... but really it > was the ARM server not responding. Not a real error in the code and/or > build itself. > > How should we handle this? > > Can we ignore it if the build server is dead/slow/not responding? > Or should we simply disable the ARM builds? > > -- > Best regards / Met vriendelijke groeten, > > Niels Basjes >
