Re: Build box gone bad

2013-09-28 Thread Erik de Bruin
Ok, have changed the builds to 'hourly', and they don't seem to stack up, only one of each is allowed in the queue. I'll try that for a while, see if that serves us better. EdB On Sat, Sep 28, 2013 at 1:11 PM, Erik de Bruin wrote: > The way the cycling through the FP/AIR version combinations

Re: Build box gone bad

2013-09-28 Thread Erik de Bruin
The way the cycling through the FP/AIR version combinations works needs a continual loop. If we set it up to be only triggered by a git change, that means that that change is tested only against one possible combination right away, and will only be fully verified after three more commits. I'm goin

Re: Build box gone bad

2013-09-28 Thread Justin Mclean
Or only build on a git change? On 28/09/2013 4:42 PM, "OmPrakash Muppirala" wrote: > Can you just set it up with every hour on each build? We have only one > slave so the others will be queued. They will have to run sequentially > then. > > Thanks, > Om > > > On Fri, Sep 27, 2013 at 11:26 PM, E

Re: Build box gone bad

2013-09-27 Thread OmPrakash Muppirala
Can you just set it up with every hour on each build? We have only one slave so the others will be queued. They will have to run sequentially then. Thanks, Om On Fri, Sep 27, 2013 at 11:26 PM, Erik de Bruin wrote: > Yeah, sorry about that. > > It's set up that way because the time it takes t

Re: Build box gone bad

2013-09-27 Thread Erik de Bruin
Yeah, sorry about that. It's set up that way because the time it takes to run any of these suites varies significantly. I want them to run as often as possible, so as soon as one of them is done, it launches the next... in a loop. Loops are never a really good idea, especially when Java is involve

Re: Build box gone bad

2013-09-27 Thread OmPrakash Muppirala
On Fri, Sep 27, 2013 at 8:50 PM, OmPrakash Muppirala wrote: > I will take a look at what is going on. I've disabled the builds for > now. > > Thanks, > Om > > P.S. The credentials for this VM was sent to the private list by Erik a > while ago. > > Looks like a build loop was created and the VM r

Re: Build box gone bad

2013-09-27 Thread OmPrakash Muppirala
I will take a look at what is going on. I've disabled the builds for now. Thanks, Om P.S. The credentials for this VM was sent to the private list by Erik a while ago. On Fri, Sep 27, 2013 at 4:53 PM, Justin Mclean wrote: > Hi, > > Looks like it's run out of memory and is spamming the com