On Fri, Apr 27, 2007 at 03:52:48PM +0200, Bernd Eilers wrote:
> >>Thorsten Ziehm wrote:
> >>[... snip ...]
>
> >Please note that I just also learned that tests for milestones seem to
> >be done on tinderbox only recently for newer milestones thus for older
> >milestones only information for CWSs based on milestones is available in
> >the new TreeView in EIS.
>
> I just got some new background information:
>
> The way Tinderbox handles information about milestone builds is that
> only information about the last 3 milestones on a masterworkspace is
> being kept. Builds on milestones are repeated as long as the build
> breaks on them and a patch is available.
Some clarification: If it breaks, a patch for that break is applied. If
there is another breaker, then another patch is added in addition to the
first one, and so on, until the master builds OK with the patches
applied. (this is what is meant with "repeated as long as the build
breaks")
The patches applied are listed in the build-status box on the status
page of the cws/Master. (at least the mac and linux tinderboxes does
this)
For example, for m211, the mac tinderbox applies patches for issue
76616 and issue 75975 (both are minor WaE fixes when building with gtk
enabled)
These patches are applied to every cws that is based upon that
milestone.
Every milestone that is no longer listed (and is more recent than m180)
can be assumed to have been built OK.
So unless your cws is based on the latest master and that status is not
yet available or not yet green, then any breaker is caused by your cws
(or one of the false positive conditions)
ciao
Christian
--
NP: Linkin Park - Somewhere I Belong
Join #qa.OpenOffice.org on irc.freenode.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
