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
AVRO-3933: Unify ARM64 workflows #2722
base: main
Are you sure you want to change the base?
AVRO-3933: Unify ARM64 workflows #2722
Conversation
@martin-g This PR is a POC to unify the ARM64 workflow with the regular x64 based workflow. The most important thing is that the same (as much as possible) worklfow is used for x64 and ARM64 (using build matrix). @nielsbasjes Not sure if this PR is a step back for your issue yesterday |
I'm fine with this step as soon as the ARM build servers are reliable. Are these servers reliable now? Note that the README.md also needs changes as part of this merge request. |
Roger. So based on your PR you just wanted simply make it visible that ARM failed, so we can ignore it (since it is an issue of the self hosted runner) |
Using the github hosted |
Yes exactly. Before my patch it showed that the Java build failed. A deeper dive into the logging was needed to reveal that it was the ARM runner ... again. With this split this became easier to inspect. I fully like your approach to consolidate the builds over all architectures. |
Apparently simply having this in Github Actions has been a feature request for about 2 years now actions/runner-images#5631 |
Yeah, it is a big missing piece from Github. Hopefully soon it is released. Github announced last year that ARM runners are coming this year. |
What is the purpose of the change
Unify ARM64 build workflows (AVRO-3933)
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Documentation