On Sun, Mar 20, 2011 at 9:44 AM, David Bolen wrote:
> Nick Coghlan writes:
>
>> I don't want to give up completely on the idea just yet, but I'll
>> experiment in the sandbox before I turn it back on.
>
> If you get to that point again, I'd also be willing to pick a time to
> manually check out t
Nick Coghlan writes:
> I don't want to give up completely on the idea just yet, but I'll
> experiment in the sandbox before I turn it back on.
If you get to that point again, I'd also be willing to pick a time to
manually check out the right branch or whatever and try it manually
on one of two o
On Sun, Mar 20, 2011 at 5:52 AM, Antoine Pitrou wrote:
>> I suspect, however, that as soon as something else commits to the 3.x
>> branch and causes a new test, that test_crashers (presumably from
>> changeset 9c6dcb5d8f01) will likely just take the slaves down again.
>
> The test is already disab
On Sat, 19 Mar 2011 15:41:51 -0400
David Bolen wrote:
>
> Thanks. Is that a single button somewhere or do I need to cancel the
> pending builds individually when there are several waiting?
There seems to be a single button.
> In any event it looks like the retries of the failing 3.x build
> st
Antoine Pitrou writes:
> I've enabled the button to cancel pending builds in the Web UI. You
> should be able to bring back the Ubuntu slave online. You can do the
> same (cancel pending builds) for other slaves if needed.
Thanks. Is that a single button somewhere or do I need to cancel the
pen
On Sat, 19 Mar 2011 14:45:10 -0400
David Bolen wrote:
>
> The problem is that the failing build is automatically retried when I
> try to reconnect the buildbot, so it just get rights into trouble
> again. The comment in that build's changeset looks like it might be
> getting rolled back?
>
> As
I've run out of virtual memory on my Ubuntu buildbot today (and I
think the FreeBSD buildbots a few days ago). Those have physically
OOMd/restarted the VM. The Windows buildbots have been giving me
VM warnings, but appear to have gotten through it.
I believe it's the test_crashers test, which wh
