Still looking for volunteer to run Windows buildbot
Josiah Carlson told me had has given up getting a Windows buildbot running, because every time he installed VS.NET on his machine, the installation would immediately crash. So if anybody wants to contribute both a machine and time to operate it (including the likely very tedious phase to get any results out of this at all), please contact me. Regards, Martin
Martin v. Löwis wrote:
Josiah Carlson told me had has given up getting a Windows buildbot running, because every time he installed VS.NET on his machine, the installation would immediately crash.
So if anybody wants to contribute both a machine and time to operate it (including the likely very tedious phase to get any results out of this at all), please contact me.
Are there any estimates how much network traffic a buildbot would generate? And how must it be connected to the internet - I assume it must be reachable from the outside. Thomas
[Thomas Heller]
Are there any estimates how much network traffic a buildbot would generate?
It should be trivial except for the initial checkout of the Python code base.
And how must it be connected to the internet - I assume it must be reachable from the outside.
The slave opens a socket connection to the master, so you must be able to reach the python.org box _from_ the slave. I don't expect you'll have serious problems if you can do that much. For example, my home box has a dynamic IP (assigned by my ISP to my router), my router gives a different dynamic IP to my box (NAT'ed), and I'm running behind both software and hardware (SPI) firewalls. Because my box initiated the connection, nothing in the chain objects.
Thomas Heller wrote:
Are there any estimates how much network traffic a buildbot would generate?
It will need to download the entire source code twice (once for the trunk, and once for 2.4). After that, it currently does only svn up, on each commit.
And how must it be connected to the internet - I assume it must be reachable from the outside.
No: it opens a connection itself, and then keeps that connection permanently open. Regards, Martin
On Sat, Mar 11, 2006 at 07:08:14PM +0100, Thomas Heller wrote:
Martin v. L?wis wrote:
Josiah Carlson told me had has given up getting a Windows buildbot running, because every time he installed VS.NET on his machine, the installation would immediately crash.
So if anybody wants to contribute both a machine and time to operate it (including the likely very tedious phase to get any results out of this at all), please contact me.
This is an ideal job for VMWare on an existing linux build machine if someone can ante up a win xp and msvc++ license to the cause. A vmware license for the build host probably isn't even necessary assuming vmware player works and one of us with a license can setup the vmware image (http://www.vmware.com/products/player/). (theres also a chance we could get vmware inc. to donate a license to python if one was needed)
Gregory P. Smith wrote:
On Sat, Mar 11, 2006 at 07:08:14PM +0100, Thomas Heller wrote:
Martin v. L?wis wrote:
Josiah Carlson told me had has given up getting a Windows buildbot running, because every time he installed VS.NET on his machine, the installation would immediately crash.
So if anybody wants to contribute both a machine and time to operate it (including the likely very tedious phase to get any results out of this at all), please contact me.
This is an ideal job for VMWare on an existing linux build machine if someone can ante up a win xp and msvc++ license to the cause. A vmware license for the build host probably isn't even necessary assuming vmware player works and one of us with a license can setup the vmware image (http://www.vmware.com/products/player/). (theres also a chance we could get vmware inc. to donate a license to python if one was needed)
Right. I have setup 64-bit Ubuntu on a new Athon64 machine, created WinXP and WinXP64 empty virtual machines with VMWare workstation, then installed XP and XP64 into these images. The images run on the Ubuntu machine in VMWare player. I don't think we need more x86 or x86-64 buildbots, so I made no attempt to install the buildbots. Thomas
On 3/29/06, Gregory P. Smith
This is an ideal job for VMWare on an existing linux build machine if someone can ante up a win xp and msvc++ license to the cause.
It probably isn't great from a practical point of view if you wanted to run buildbot for both the server and host platforms. The problem is that jobs for both platforms will be scheduled concurrently. If checkins occur in both 2.5 and 2.4 as is somewhat common, you would be running 4 test suites simultaneously. The full suite already takes quite a bit of time (over 20 minutes depending on the box). The machine could be crushed if we run 4. If you just wanted to run Windows in VMware, that would be fine. We already have 3 windows buildbots of the XP and 2k variety. Other varieties might be desirable. n
participants (5)
-
"Martin v. Löwis" -
Gregory P. Smith -
Neal Norwitz -
Thomas Heller -
Tim Peters