Boost Testing :
From: Rene Rivera (grafik.list_at_[hidden])
Date: 2005-04-25 00:04:53
David Abrahams wrote:
> Rene Rivera <grafik.list_at_[hidden]> writes:
>>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.
10 minutes is as short as I'd make it given the limitations of CVS.
Using SVN would be a different story as we can, with sufficient
developer care, get cohesive change updates.
As for restart testing function.. I think it's already in there. It's
already possible to click on the info for an ongoing build (the link for
"Build #") and that has a button to stop the build. I suspect, haven't
tried this, that if one stops an ongoing build and there are other
builds queued up it will start another one immediately.
-- -- 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