Hi *, On Thu, Feb 08, 2007 at 12:58:57PM +0100, Bernd Eilers wrote: > > Status from tinderbox builds is now integrated into the ChildWorkspace > overview page. Please watch out for anything that´s "red" there, because > this means the build fails. In this case someone should have a closer > look why. There can be 3 reasons: > > 1.) Network problem with collabnet. Unable to check out source code or > similar ( can be ignored ).
New modules fall into that category as well. When your cws introduces a new module, you can ignore the status as well. > 2.) The CWS introduced a bug making the source code not buidable on one > of the platforms testet by tinderbox. In this case please file an issue > and reset the status of the CWS from "ready for qa" to "new". > > 3.) There is a build problem in the source code but the CWS inherited it > from the master ( problem already in the master ). In this case, make > sure an issue exists. To check whether the bug is in the master already, you can use the http://go-oo.org/tinderbox/ready_for_QA.express.html overview page. That page lists the three most recent master milestones. For older milestones, the tinderbox-admins usually have already hunted down the necessary patches and apply them to the builds, but if you want to check nevertheless, you can try http://go-oo.org/tinderbox/<your master>.express.html e.g. http://go-oo.org/tinderbox/SRC680_m196.express.html to check whether other cws based on that milestone break as well ciao Christian -- NP: Bif Naked - Any Day Now --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
