Hi Peter, *, On Jan 9, 2008 3:25 AM, Peter Junge <[EMAIL PROTECTED]> wrote: > > additionally there seems to be a 'Violet' state. What does that mean?
The colors are explained at the bottom of every status page, see e.g. http://tinderbox.go-oo.org/chart15/status.html Build State Cell Colors grey: Build interrupted or rejected by the buildslave violet There have been commits after the build started white Build in progress - status unavailable yellow Build in progress - status available red Build failed orange Build succeeded but tests failed green Build and all tests were successful The only thing it doesn't specify is what "tests" are.. But let me explain the colors: grey: The bot knows that it cannot build a master because it is too broken (like m237), then it refuses to build any cws based on that milestone and sets the "fold" status that will mark the build with grey. This status should be used as well, when there botmaster loses the connection with the buildslave or similar. Unfortunately this is not the case yet, the botmaster still sets the failed state (red) in this case lila/purple/violet: The old buildresults are no longer valid, since there were commits to the cws. The new commits might have broken the build or might have fixed a buildbreaker - so whatever the result of the last build was, you cannot be sure whether that result will be the same when you rebuild the cws with the new commits. (Of course you can still have a look at the old logs if you know what the new commits are about and decide whether the results could be affected or not.) yellow: Build is running - no result available. Some bots will upload the configure output at this stage, others just send a "I did start a build" like info. red: This is the only state where QA/Devs need to take action. This is the state where a build broke because of a build error. green: Everything was OK, the cws built without any problem. Note that the bots don't do any functionaliy testing, this just means that an installation set could be produced, not that OOo will work as expected. orange: The built completed, but there were problems during the build. Only the Mac X11 tinderbox uses this state currently. In this case it means that the build did not complete in one run, that it had to rebuild one or more modules more than once (most likely because of regcomp failing). What modules it needed to rebuilt is annotated in the build info-box on the status page. HTH, ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
