Mailman 3 - Python-Buildbots

Partial Git clones and disk space
by Victor Stinner 1 জুন, 2026

1 জুন, 2026

Hi, A change has been merged into the Python buildbots to use partial ("blobless") git clones: https://github.com/python/buildmaster-config/pull/729 If your buildbot worker disk space is low, you can stop the buildbot client, remove build directories, and then restart the buildbot client. Be careful to not remove the client configuration by mistake (buildbot.tac and twistd.hostname files). New builds should now use Git partial clones. Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

skumaran-ubuntu-x86_64 worker offline
by Senthil Kumaran 1 জুন, 2026

1 জুন, 2026

Hello Team, I am consolidating the providers I use for hosting. I am taking my buildbot skumaran-ubuntu-x86_64 offline for a short time. I will bring up a new host, and I am open to bringing up a new operating system if there a coverage to be desired. I can also bring up an Intel Mac if that is required. If not, I will bring up another Ubuntu for the replacement of .skumaran-ubuntu-x86_64 worker . Please review and merge this. https://github.com/python/buildmaster-config/pull/731 Thank you, Senthil

1 0

CPython Intel macOS buildbot disk failure
by Matt Billenstein 27 মে, 2026

27 মে, 2026

Will be offline a few days - have a refurb'd disk on the way. m -- Matt Billenstein matt(a)vazor.com https://vazor.com

1 1

Re: CPython Intel macOS buildbot disk failure
by Zachary Ware 19 মে, 2026

19 মে, 2026

On 5/19/26 13:17, Matt Billenstein via Python-Buildbots wrote: > Will be offline a few days - have a refurb'd disk on the way. Thanks for the heads-up!

1 0

buildbot for Windows11 pro
by Deepthi B 5 ফেব্রুয়ারি, 2026

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 19 ডিসেম্বর, 2025

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 1 সেপ্টেম্বর, 2025

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 27 আগস্ট, 2025

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 2 জুন, 2025

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 3 ডিসেম্বর, 2024

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