On Mon, Dec 30, 2013 at 12:18 PM, Christian Heimes <christ...@python.org> wrote: > Am 30.12.2013 15:02, schrieb Chris Angelico: >> On Tue, Dec 31, 2013 at 12:05 AM, Chris Angelico <ros...@gmail.com> wrote: >>> On Sun, Dec 8, 2013 at 12:35 AM, Chris Angelico <ros...@gmail.com> wrote: >>>> 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? >>> >>> Is there any interest in this build slave? I haven't heard back from >>> anyone as to where to go from here. >> >> Antoine's contacted me off-list and sorted out the details. Bruce the >> Aussie Buildbot is now in operation. (And yes, the hostname is >> 'bruce'.) >> >> Thanks Antoine! > > Thanks guys! > > The buildbot is missing some vital header files. Please run: > > # apt-get build-dep python3.3 > > to install all required dependencies.
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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
