Buildbot running Debian amd64 as root

In another thread it was suggested that a new buildbot running as root would be of value. I've spun up a virtual machine running Debian Wheezy amd64, have installed buildbot from the repository (version 0.8.6p1), and am ready to have it join the farm. How do I go about doing this? I've followed the instructions in https://wiki.python.org/moin/BuildBot as far as creating the slave. There's a user named buildbot but I'll be running the buildslave command as root - that would do it, right? Which means I just need to set up a name and password. The VM has 1GB RAM and is permitted up to two cores of my i5 CPU, and has 120GB disk space available. It's running behind NAT, which should be safe against accidental problems, but not malicious compromise. I'll look into firewalling it off to keep things safeish but mainly I'm trusting that Python core devs aren't going to be attacking my network :) ChrisA

On Mon, Dec 30, 2013 at 12:18 PM, Christian Heimes <christian@python.org> wrote:
It looks like it compiled and ran the tests fine, except for two failures due to a lack of zlib. If zlib is a required dependency, the build process should die without it (or fall back to the version living in Modules/zlib), and needs to be fixed. If it is as optional as it seems to look, then it might be good to keep a buildbot that explicitly doesn't have all (or even any) of the optional dependencies and we should just fix the tests that expect zlib unconditionally. Perhaps not this buildbot, though, since it's the only one running as root. Either way, this buildbot's first and thus far only run has already shown up something that needs to be fixed ;) -- Zach

On Mon, Dec 30, 2013 at 2:31 PM, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
and we should just fix the tests that expect zlib unconditionally.
Both of which turned out to be trivial; the import of zlib was already guarded in both places, but one skip was checking the wrong name and the other just didn't try to skip, so I've fixed both. -- Zach

On Mon, 30 Dec 2013 15:00:02 -0600, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
We've gone through spates before of fixing the tests that rely on various optional modules (especially zlib). Yeah, having a buildbot configured without all the optional modules would be nice. --David

On Tue, Dec 31, 2013 at 5:18 AM, Christian Heimes <christian@python.org> wrote:
Debian Wheezy doesn't package 3.3 but only 3.2, so I grabbed 3.2's build-deps. They're now installed, so the next build should have everything for that. Does anyone happen to know what (if anything) 3.3 needs that 3.2 doesn't? I hit Force Build on the 3.3 one, so hopefully that'll show up. It's busily checking out now. ChrisA

On Mon, Dec 30, 2013 at 12:18 PM, Christian Heimes <christian@python.org> wrote:
It looks like it compiled and ran the tests fine, except for two failures due to a lack of zlib. If zlib is a required dependency, the build process should die without it (or fall back to the version living in Modules/zlib), and needs to be fixed. If it is as optional as it seems to look, then it might be good to keep a buildbot that explicitly doesn't have all (or even any) of the optional dependencies and we should just fix the tests that expect zlib unconditionally. Perhaps not this buildbot, though, since it's the only one running as root. Either way, this buildbot's first and thus far only run has already shown up something that needs to be fixed ;) -- Zach

On Mon, Dec 30, 2013 at 2:31 PM, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
and we should just fix the tests that expect zlib unconditionally.
Both of which turned out to be trivial; the import of zlib was already guarded in both places, but one skip was checking the wrong name and the other just didn't try to skip, so I've fixed both. -- Zach

On Mon, 30 Dec 2013 15:00:02 -0600, Zachary Ware <zachary.ware+pydev@gmail.com> wrote:
We've gone through spates before of fixing the tests that rely on various optional modules (especially zlib). Yeah, having a buildbot configured without all the optional modules would be nice. --David

On Tue, Dec 31, 2013 at 5:18 AM, Christian Heimes <christian@python.org> wrote:
Debian Wheezy doesn't package 3.3 but only 3.2, so I grabbed 3.2's build-deps. They're now installed, so the next build should have everything for that. Does anyone happen to know what (if anything) 3.3 needs that 3.2 doesn't? I hit Force Build on the 3.3 one, so hopefully that'll show up. It's busily checking out now. ChrisA
participants (5)
-
Chris Angelico
-
Christian Heimes
-
R. David Murray
-
Zach Ware
-
Zachary Ware