Am Montag, 13. Oktober 2008 02:27:20 schrieb Giel van Schijndel: > [EMAIL PROTECTED] schreef: > > The Buildbot has detected a new failure of nightly_mingw32 on Warzone > > 2100: Resurrection Project. Full details are available at: > > http://build.kynes.de/builders/nightly_mingw32/builds/17 > > > > Buildbot URL: http://build.kynes.de/ > > > > Buildslave for this Build: i386-debian-etch-2 > > > > Build Reason: The Nightly scheduler named 'nightly' triggered this build > > Build Source Stamp: HEAD > > Blamelist: > > > > BUILD FAILED: failed compile warnings+1 > > Erm.... Why does it report failure? The build clearly succeeded... (i.e. > [1] and [2] are produced as a result of it).
The reason for the build being marked as failure lies here: "failed compile warnings+1" See http://build.kynes.de/builders/nightly_mingw32/builds/17/steps/warningscounter/logs/changes for which additional warning sliped in yesterday. Actually the buildbot works exactly as desired. :) What might have caused your confusion is that a buildbot build can run through all steps completely, even if the overall build will be marked as a failure. I decided an increase in warnings to be a failure, so we get this email notification and people care more. --Devu
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
