Hello, This is expected as Equinix (the hosting company of the machine) is decommissioning all its fleet. Arm has donated an Arm server to the PSF that will replace this worker.
It’s still sitting in my office as we are waiting our IT department to make all the network adjustment to properly host it. I’ve been told that it will be in the coming weeks. I did a backup and made notes of all the changes we did, so it could be “easily” restored. Note for Pablo/Łukasz: the worker decommissioned is the same machine that ran benchmarks for speed.python.org. So, for the time being we won’t have AArch64 results in there. From the buildbot point of view, do I need to raise any PR to temporary disable the worker? --Diego From: build...@python.org <build...@python.org> Date: Friday, 29 August 2025 at 18:19 To: Subject: Buildbot Python worker diegorusso-aarch64-bigmem missing The Buildbot worker named diegorusso-aarch64-bigmem went away. It last disconnected at Fri Aug 29 16:19:27 2025. The admin on record (as reported by WORKER:info/admin) was Diego Russo <diego.ru...@arm.com> . IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ Python-Buildbots mailing list -- python-buildbots@python.org To unsubscribe send an email to python-buildbots-le...@python.org https://mail.python.org/mailman3//lists/python-buildbots.python.org Member address: arch...@mail-archive.com
