Skip to content
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

Run CI on Github-hosted Arm instances too #5145

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Rohanjames1997
Copy link

Extend the CI to run on Github-hosted Arm instances that are now available.

Note that running on ubuntu-24.04-arm currently fails with E: Unable to locate package libtinfo5.

@rgommers
Copy link
Contributor

Thanks @Rohanjames1997. Could you please elaborate on what this tests that wasn't already tested? I suspect that this overlaps with the Cirrus CI NeoverseN1 jobs.

@Rohanjames1997
Copy link
Author

Thanks @rgommers. I actually didn't know of the Cirrus CI jobs, I just saw them 😄
I thought all the CI scripts were on Github Actions.

And you're right, while the ubuntu-22.04-arm runner is a NeoverseN2 CPU, this would still overlap with the Cirrus NeoverseN1 job or the one in dynamic_arch.yml

I guess I can close this if it doesn't add any additional testing.

@martin-frbg
Copy link
Collaborator

martin-frbg commented Feb 22, 2025

There is already an Arm-on-gh runner (added to the bottom of the dynamic_arch job by #5080 right when these runners became available), but it is currently executing on Neoverse N1 (exactly like the pre-existing Cirrus jobs) rather than N2 as gh had to pull back the runners from the new Cobalt-100 hardware to generic dpdsv5 instances due to software issues - see https://github.com/orgs/community/discussions/148648#discussioncomment-12205917

@martin-frbg
Copy link
Collaborator

Long- term it would probably make sense to move the comparable Arm64 jobs from Cirrus to gh as we tend to run out of free minutes there towards the end of the month. But this needs to wait until the end of the current "public beta" when it becomes clear what they plan to provide to opensource projects on a permanent basis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants