[users at bb.net] High trigger time using Triggerable Scheduler
Povilas Kanapickas
povilas at radix.lt
Fri Mar 19 20:23:42 UTC 2021
You could have a master lock
(https://buildbot.readthedocs.io/en/latest/manual/configuration/interlocks.html)
with maxCount=20 and attach it to all the builders that e.g. produce a
lot of logs.
On 3/19/21 10:16 PM, Vlad Bogolin wrote:
> Hi,
>
> I did some investigations and I think the issue is caused by an
> overloaded master. The master process constantly uses around 120% CPU
> and doesn't drop at all below 100%. Is there any way to have a hard
> limit on the number of builds that can be run (e.g always run at most 20
> builds)?
>
> Thanks!
>
> On Fri, Mar 19, 2021 at 7:55 PM Vlad Bogolin <vlad at mariadb.org
> <mailto:vlad at mariadb.org>> wrote:
>
> Hi,
>
> Thanks for the reply! No, waitForFinish is False. In a normal
> scenario, this took a couple of minutes. Now, we have runs that even
> have 1h.
>
> Thanks,
> Vlad
>
> On Fri, Mar 19, 2021 at 6:44 PM Povilas Kanapickas <povilas at radix.lt
> <mailto:povilas at radix.lt>> wrote:
>
> Hi,
>
> Could you please check if you're using waitForFinish=True
> argument for
> the trigger step? That would wait for all triggered builds to
> finish.
>
> Cheers,
> Povilas
>
> On 3/19/21 1:50 PM, Vlad Bogolin wrote:
> > Hi,
> >
> > We have a problem in our configuration where the trigger time
> for 71
> > builds is very high (sometimes even up to 1 hour). For example
> > here https://buildbot.mariadb.org/#/builders/1/builds/13508, the
> > triggering step (step 12) took 57 mins. This problem only
> started to
> > occur recently without having any changes to the triggering
> procedure.
> > Do you have any suggestions on what might be causing this?
> >
> > Thanks,
> > Vlad
> >
> > _______________________________________________
> > users mailing list
> > users at buildbot.net <mailto:users at buildbot.net>
> > https://lists.buildbot.net/mailman/listinfo/users
> >
>
>
>
> --
> Vlad
>
>
>
> --
> Vlad
More information about the users
mailing list