Hi Eric, *, On Mon, Dec 11, 2006 at 08:37:05PM +0100, eric b wrote: > [...] > The problem is very simple : they are tagged milestones, and these > one are not buildable with the corresponding source code, because > build fixes will be integrated in the next one. > [...] > This problem is fully repeatable, and will certainly (unfortunaly ) > occur again. > [...] > So, I have a proposal : > step 1 : > tag odd milestones > odd milestones will contain previous milestones + all integrated cws > step 2 : > build all concerned architectures : > Windows, > Linux > Solaris > Mac O SX > ... > > Comment : buildbots for Mac OS X + manual builds should be enough. > I'm pretty sure this is the same for other archs :-)
I know everybody is on the buildbot-hype - but don't forget about tinderbox.. Tinderbox constantly builds everything without an explicit request to do so. Many buildbreakers can just be avoided by not integrating cws that break the build. (Preventing is better than fixing afterwards) Tinderbox has a seperate overview page for cws that are in ready-for-qa state[1]: http://go-oo.org/tinderbox/ready_for_QA.express.html (main builders are two linux boxes (build everything), one PPC Mac (builds everying) and one Windows-box (builds selected stuff)) So before a cws gets nominated, I suggest that the QA-Rep has a look at that page. If the cws is listed "green", then no problem, nominate it. However if one or more are listed "red", then have a look at the logs (tinderbox offers summarized logs as well as full logs) and see whether the breaker is caused by the cws. You can ignore the "red" status if * You added a new module (is not listed in EIS info and thus tinderbox cannot know about it, the build will break because of that missing module) * the Master your cws is based on failed as well. Usually the buildmaster of the buildslave will hunt for patches in IZ and apply them to make the master build and then rebuild all relevant cws so this should only last a couple of days) Apart from that, a build may occasionaly fail because of parallel build issues, but that is the exception, not the rule. If your cws is red, and the master is green, then something is fishy. Have a look! If tinderbox didn't build your cws yet, fire up one of the buildbots to fill the gap. Tinderbox buildslaves will always perform clean builds (as do the buildbots). combinations of integrated cws may still cause build-breakers, but well, that's life... > [...] ciao Christian [1] other overview pages are only "new" cws: http://go-oo.org/tinderbox/new.express.html and both ready and new: http://go-oo.org/tinderbox/all_trees.express.html -- NP: Body Count - Last Breath --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
