Re: [testing] Buildbot setup status.
Robert Ramey wrote:
It looks like it runs even before I finish getting a whole group of changed checked in.
It's on a 10 minute trigger. So it waits for 10 minutes where it hasn't gotten CVS notifications before proceeding. Looks like you had the commits spaced out in 20, or so, minutes. This is one of those, tweak until we get what's appropriate for Boost development. Should I make that longer? 20, 30, 60 minutes? I don't want to make it feel unresponsive though. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
Rene Rivera <grafik.list@redshift-software.com> writes:
Robert Ramey wrote:
It looks like it runs even before I finish getting a whole group of changed checked in.
It's on a 10 minute trigger. So it waits for 10 minutes where it hasn't gotten CVS notifications before proceeding. Looks like you had the commits spaced out in 20, or so, minutes.
This is one of those, tweak until we get what's appropriate for Boost development. Should I make that longer? 20, 30, 60 minutes? I don't want to make it feel unresponsive though.
I say keep a short (maybe even shorter!) trigger, and make a "restart all testing" button available for those rare cases when a developer knows an outdated and broken state is being tested. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (2)
-
David Abrahams -
Rene Rivera