Opened at 2007-12-19T00:07:36Z
Closed at 2008-03-05T00:31:15Z
#238 closed enhancement (fixed)
make the slowest buildslaves faster
Reported by: | zooko | Owned by: | zandr |
---|---|---|---|
Priority: | minor | Milestone: | eventually |
Component: | dev-infrastructure | Version: | 0.7.0 |
Keywords: | Cc: | ||
Launchpad Bug: |
Description
http://allmydata.org/buildbot/waterfall?show_events=false
The fastest buildslaves can usually finish in about 2 minutes, but the slowest ones often take more than 20 minutes. This is unfortunate because it leaves me uncertain whether I've just broken the unit tests on the slowest systems (cygwin, edgy, and feisty).
I think what is going on is that these three are all running on virtual machines hosted on the same actual machine, is that right?
Maybe they would run all to completion faster if we staggered them.
Change History (2)
comment:1 Changed at 2007-12-19T01:39:08Z by warner
- Owner changed from zamdr to zandr
comment:2 Changed at 2008-03-05T00:31:15Z by zandr
- Resolution set to fixed
- Status changed from new to closed
Closing as done.
At present:
virtual1: Etch and Cygwin virtual2: Windows Native and Nevow virtual3: Edgy and Feisty
hmm maybe. I think windows is going to be slower anyways, but I'd be happy to set up an exclusion to make the other builders that share a CPU to wait like 2 minutes before starting in the hopes of getting the cygwin to finish sooner.
zandr: what's the current mapping from buildslave to physical host?