On Fri, Mar 23, 2007 at 10:17:04AM +0000, Shaun McDonald wrote:
> On 23 Mar 2007, at 09:33, Kay Ramme - Sun Germany - Hamburg wrote:
> [..]
> How many CWS are there at any one time open?
>130
> How long does a build
> take?
About 2 1/2 hours
> How far behind would the box/bot be if the compilation were to
> happen more often?
See my other post. The 7-10 days penalty only applies to failed cws when
there have been no changes. Rebuilding stuff that did not change is a
waste of ressources.
> >>But again: Why would a retrigger be necessary? A build will take 3-4
> >>hours or longer, so you're surely not sitting right next to it and
> >>wait
> >>for it to finish... Most likely you will go home before it
> >>finished :-)
> >Yes, but this is still a difference compared to 7 days. Anyway, if
> >I understand you right, you suggest to just re-trigger builds on
> >the buildbots , instead of having a button in EIS. Which is fine
> >for me as well, as long as I can somehow influence that tinderbox
> >status actually reported in EIS.
> The tinderbox status doesn't state the date/time of the last build on
> each tinderbox.
?? Of course it does.
Click on the column-header and it will tell you the "previous end time"
and the "current dead time" (the time since the last build)
Please folks, If you're not sure, ask. But don't make false claims.
ciao
Christian
--
NP: Blind Guardian - And The Story Ends
Join #qa.OpenOffice.org on irc.freenode.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
