[Buildbot-devel] Triggerable getting triggered but stays in idle state

[Andreas Johnsson]

Hi,

maxbuilds solved the problem, it was set to 1, thank you for your help :)

//
Andreas

On Fri, Feb 11, 2011 at 10:35 PM, Andreas Johnsson <
andreas.johnsson at tarsier.se> wrote:

> Hi,
> Thank you for your quick answers.
> It is on the same slave, so that sounds like the problem. I'll try to add
> another slave tomorrow and see if that helps. Thank you once again.
>
> //
> Andreas
>
>
> On Fri, Feb 11, 2011 at 6:49 PM, Amber Yust <ayust at yelp.com> wrote:
>
>> (Assuming maxbuilds is set.)
>>
>> ~Amber
>>
>>
>> On Fri, Feb 11, 2011 at 9:47 AM, Dustin J. Mitchell <dustin at v.igoro.us>wrote:
>>
>>> On Fri, Feb 11, 2011 at 11:43 AM, Amber Yust <ayust at yelp.com> wrote:
>>> > Hm. I have a similar setup on one of our buildbots (one build that
>>> triggers
>>> > ~5 others, waits for those to complete, and then continues), and it
>>> seems
>>> > work work fine. We're currently running 0.8.3 though, so I'm not sure
>>> if
>>> > it's an issue with 0.8.2 that you're experiencing, or some other
>>> factor?
>>>
>>> Do both builders want the same slave?  The triggering build will hold
>>> onto the slave, preventing the triggered build from using it.
>>>
>>> Dustin
>>>
>>
>>
>
>
> --
> Andreas Johnsson | Technical Director | Tarsier Studios AB
> *Please consider the environment before printing this e-mail*
>
>


-- 
Andreas Johnsson | Technical Director | Tarsier Studios AB
*Please consider the environment before printing this e-mail*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://buildbot.net/pipermail/devel/attachments/20110214/060f19ab/attachment.html>