Mailman 3 - Python-Buildbots

buildbot for Windows11 pro
by Deepthi B Feb. 5, 2026

Feb. 5, 2026

What should I install to run build Bot on my windows11 ? Thanks

2 1

Stuck process after test failure - looks like test_profiling's code
by Chris Angelico Dec. 19, 2025

Dec. 19, 2025

A couple of times now, I've seen my buildbot consuming a constant 100% CPU, despite not having an active build. It was a Python process running inline code, and the code itself looked like it came from Lib/test/test_profiling/test_sampling_profiler/test_integration.py (specifically, I think it's the test_script as used by test_subprocess, not the cli_test_script). A recent build seems to have had a failure in that test: https://buildbot.python.org/all/#/builders/345/builds/12988/steps/6/logs/wa… https://buildbot.python.org/all/#/builders/345/builds/12988/steps/6/logs/st… which ended with a segfault. Is this something that's likely to happen again in the future, and thus should I devise a script that will find and kill rogue processes? Or is this preventable within the test suite? ChrisA

2 2

FW: Buildbot Python worker diegorusso-aarch64-bigmem missing
by Diego Russo Sept. 1, 2025

Sept. 1, 2025

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: buildbot(a)python.org <buildbot(a)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.russo(a)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.

2 2

How to detect running under a buildbot?
by Jason R. Coombs Aug. 27, 2025

Aug. 27, 2025

In https://github.com/python/cpython/issues/132947, I'm struggling with an elusive issue where ResourceWarnings are emitted but only on a handful of buildbots. I'm unable to replicate the issue in GitHub CI or locally. So for a temporary workaround, I want to disable the test that surfaces the warning, but only in buildbots. I've been thusfar unsuccessful in finding a way to detect if the tests are running under buildbot. It seems that there's not a standard environment variable to signal running under buildbot. Could one be added so that it's possible to detect the environment in which its running? Secondarily, and maybe more importantly, any ideas why the behavior would be so different under this handful of <https://github.com/python/cpython/issues/132947#issuecomment-3217384492> buildbots<https://github.com/python/cpython/issues/132947#issuecomment-3217384492>?

4 5

skumaran buildbot
by Senthil Kumaran June 2, 2025

June 2, 2025

I am trying to bring my buildbot agent back. when I try to restart, I get the error. 2025-06-01 19:58:03+0000 [Broker,client] ReconnectingPBClientFactory.failedToGetPerspective 2025-06-01 19:58:03+0000 [Broker,client] unauthorized login; check worker name and password 2025-06-01 19:58:03+0000 [-] Scheduling retry 1 to connect <twisted.internet.endpoints.TCP4ClientEndpoint object at 0x7fd8d1be7520> in 1.7255696538712972 seconds. 2025-06-01 19:58:03+0000 [-] Stopping factory <buildbot_worker.pb.BotFactory object at 0x7fd8d240ce50> What should I do? Tried stopping and restarting. Did master/server de-authorize or de-list my agent? Thank you, Senthil

2 2

Offer: AMD64 Debian Root Free-Threading buildbot
by Chris Angelico Dec. 3, 2024

Dec. 3, 2024

With no-GIL builds becoming more important, is there need of a second AMD64 Debian root buildbot to cover this configuration? I'm happy to host a second bot VM on the same system as the existing angelico-debian-amd64 builder. It can be given identical resources to the existing one (as of today, that's 2 CPU cores off an Intel 14700KF, 4GB RAM, and 100GB storage). ChrisA

2 2

riscv64 buildbot?
by Álvaro Figueroa Nov. 1, 2024

Nov. 1, 2024

I have built and very quickly tested buildbot-worker running in riscv64 hardware, and it seems to work without any issues so far. I have also made a Fedora 41 docker container with the buildbot module and some basic dev dependencies which will probably need adjusting once modules are compiled on it. I know that riscv64 is not even in the python architecture tiers, but I wanted to ask to this list if it makes sense for me to make this buildbot available? How does a python module developer controls on which architectures do their module gets built on? The hardware that I am using in a 64-core, 128G ram milkv pioneer so it should be able to run multiple buildbots on this hardware. If there is interest in having riscv64 buildbots available, I can also ask in the "riscv labs" working group in the riscv foundation and get some very decent hardware assigned. Cheers,

1 0

Re: EOL for old Intel Macs?
by Petr Viktorin Nov. 1, 2024

Nov. 1, 2024

Hello! Thank you for reaching out, and for your long service to the project! Your worker will be useful as long as you can/want to run it -- for anyone who runs Python on any Intel Mac or older macOS version. CPython just dropped support for macOS 10.12 (Sierra) and earlier in 3.12.6 and 3.13; Monterey is 5 years newer. If your worker goes offline, we'll be looking for a replacement -- perhaps a slightly newer Intel Mac. There's no immediate need for a M1 worker: Pablo has been running one for 9 months now: https://buildbot.python.org/#/workers/44 On 31. 10. 24 4:10, Matt Billenstein via Python-Buildbots wrote: > Hi, > > Regarding worker https://buildbot.python.org/#/workers/17 - this is a mid-2015 > Macbook Pro; the latest macOS release it can run is Monterey first released in > 2021 (12.7.6 currently). > > I just put I think the third battery in it about a year ago, so my guess is I > could keep it in service another 3-4 years (they swell and go bad after about 4 > years), but I'm wondering is a system this old still valuable to the project? > Or for how long? I have a newer M1 Macbook Pro I could replace it with or add > to the fleet. > > Please advise on what's useful to the project. Happy to keep it going, replace > it, or just add the newer M1. > > thx > > m

2 1

EOL for old Intel Macs?
by Matt Billenstein Oct. 31, 2024

Oct. 31, 2024

Hi, Regarding worker https://buildbot.python.org/#/workers/17 - this is a mid-2015 Macbook Pro; the latest macOS release it can run is Monterey first released in 2021 (12.7.6 currently). I just put I think the third battery in it about a year ago, so my guess is I could keep it in service another 3-4 years (they swell and go bad after about 4 years), but I'm wondering is a system this old still valuable to the project? Or for how long? I have a newer M1 Macbook Pro I could replace it with or add to the fleet. Please advise on what's useful to the project. Happy to keep it going, replace it, or just add the newer M1. thx m -- Matt Billenstein matt(a)vazor.com https://vazor.com

1 0

Issues with the aarch64 Fedora/RHEL/CentOS Stream buildbots
by Charalampos Stratakis Sept. 3, 2024

Sept. 3, 2024

Hi folks, I'm facing some issues with the hypervisor of the aarch64 linux buildbots. The buildbots have been offline for some time now, I'm trying to resolve some issues with the hypervisor and hopefully I'll have them running again soon. -- Regards, Charalampos Stratakis Senior Software Engineer Python Maintenance Team, Red Hat

1 1