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
On Sat, Nov 18, 2023 at 4:03 PM Chris Angelico <rosuav@gmail.com> wrote:
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).
A year later, I notice that I starred this in my email but never managed to respond. Sorry about that!
I think adding such a worker (or just adding a builder to the existing worker, especially if adding the CPU/RAM that would be given to a new worker to the existing one instead) would be welcomed; opening a PR against https://github.com/python/buildmaster-config would be the best next step when you're ready.
Thanks, Zach
On Tue, 5 Nov 2024 at 10:57, Zachary Ware <zach@python.org> wrote:
On Sat, Nov 18, 2023 at 4:03 PM Chris Angelico <rosuav@gmail.com> wrote:
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).
A year later, I notice that I starred this in my email but never managed to respond. Sorry about that!
... and then it takes me a month to respond. I'm not really a shining example of promptness myself here!
I think adding such a worker (or just adding a builder to the existing worker, especially if adding the CPU/RAM that would be given to a new worker to the existing one instead) would be welcomed; opening a PR against https://github.com/python/buildmaster-config would be the best next step when you're ready.
Adding a builder to the existing one would be convenient. I've never edited that config though, so I'm not sure what needs to be updated here.
ChrisA
participants (2)
-
Chris Angelico -
Zachary Ware