Skip to content

Conversation

@encukou
Copy link
Member

@encukou encukou commented Aug 21, 2025

Fedora/RHEL aarch64 are down. I reached out to @stratakis, who said the server was now decommissioned, work is underway to add a new server from ARM, but it might take a while.

I think it's best to mark the builders as unstable, rather than remove them. That way we shouldn't need a PR before bringing them online, but only after they're up and green for a few days.

cc @vstinner @gpshead: until the new server is racked, there's only diegorusso-aarch64-bigmem for aarch64-unknown-linux-gnu.

Copy link
Member

@StanFromIreland StanFromIreland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds like a good plan to me.

@encukou
Copy link
Member Author

encukou commented Aug 21, 2025

@itamaro, how is it looking with your macOS noGIL worker? Do you want to do the same for it?

@itamaro
Copy link
Contributor

itamaro commented Aug 21, 2025

@itamaro, how is it looking with your macOS noGIL worker? Do you want to do the same for it?

The Intel macOS worker is still down, so yes, let's mark it unstable for now, thanks @encukou !

@encukou encukou changed the title Mark cstratak-*-aarch64 builders as unstable Mark cstratak-*-aarch64 & itamaro-macos-intel-aws builders as unstable Aug 22, 2025
@encukou encukou merged commit d1e7d41 into python:main Aug 22, 2025
1 check passed
@encukou encukou deleted the aarch64-unstable branch August 22, 2025 06:44
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