Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Montag, 23. Februar 2009 02:08:10 schrieb buildbot+notif...@kynes.de: > 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/0 > > 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 Disk full... --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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
On Thu, Jan 15, 2009 at 02:07:01AM +0100, buildbot+notif...@kynes.de wrote: > 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/111 > > 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 shell_3 "File exists." -- Giel signature.asc Description: Digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
On Fri, Jan 09, 2009 at 02:00:01AM +0100, buildbot+notif...@kynes.de wrote: > 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/105 > > 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 svn Dennis, to clean up space I had to remove /var/svn/warzone and instead depend on http://svn.gna.org/svn/warzone. If you could fix up the buildbot recipe to use that checkout URL instead that should fix that ^^ problem. -- Giel signature.asc Description: Digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
On Wed, Dec 24, 2008 at 02:08:07AM +0100, buildbot+notif...@kynes.de wrote: > 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/90 > > 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 shell_3 output: > gpg: signing failed: file exists > program finished with exit code 2 Meaning: the build was already done for this revision. @Dennis: any chance you could look at preventing double builds when the first was succesfull? -- Giel signature.asc Description: Digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
buildbot+notif...@kynes.de 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/83 > > 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 shell_3 gpg: signing failed: file exists Build has been performed already. -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Samstag, 13. Dezember 2008 02:06:53 schrieb buildbot+notif...@kynes.de: > 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/79 > > 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 Compressed data: Error: deflateToFile fwrite(65536) failed when building the installer 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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Dennis Schridde schreef: > Am Freitag, 5. Dezember 2008 02:07:03 schrieb [EMAIL PROTECTED]: >> BUILD FAILED: failed compile warnings+1 > +chat_parser.y:760: warning: unused parameter 'msg' Was that way before, except that it was "hidden" that the variable wasn't used. I.e. it was used to produce some internal string buffer, but that string buffer never got used. I just removed the intermediate string buffer (was a printf-like function) because the printf-features weren't ever used. -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Freitag, 5. Dezember 2008 02:07:03 schrieb [EMAIL PROTECTED]: > 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/71 > > 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 +chat_parser.y:760: warning: unused parameter 'msg' 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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Samstag, 29. November 2008 02:08:10 schrieb [EMAIL PROTECTED]: > 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/65 > > 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 shell_3 "file exists" 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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Dennis Schridde schreef: > Am Montag, 24. November 2008 02:06:06 schrieb [EMAIL PROTECTED]: >> 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/60 >> >> 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 > Caused by recent buildsystem changes: > make[3]: *** No rule to make target `../lib/betawidget/font.c', needed by > `warzone2100.pot-update'. Stop. Fixed in r6376. -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Montag, 24. November 2008 02:06:06 schrieb [EMAIL PROTECTED]: > 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/60 > > 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 Caused by recent buildsystem changes: make[3]: *** No rule to make target `../lib/betawidget/font.c', needed by `warzone2100.pot-update'. Stop. --DevU ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Samstag, 15. November 2008 02:07:45 schrieb [EMAIL PROTECTED]: > 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/51 > > 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 +multiplay.c:1357: warning: comparison between signed and unsigned +multiplay.c:1395: warning: comparison between signed and unsigned (+1 overall, since one warning in ai.c was fixed) 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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Montag, 10. November 2008 03:08:18 schrieb [EMAIL PROTECTED]: > 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/46 > > 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+2 This means: The number of warnings was increased by 2. --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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Donnerstag, 6. November 2008 10:01:58 schrieb Giel van Schijndel: > Dennis Schridde schreef: > > Am Donnerstag, 6. November 2008 01:08:31 schrieb [EMAIL PROTECTED]: > >> 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/42 > >> > >> 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 shell_3 > > > > "file exists" > > > > Can gpg be forced to create the signature? > > Not sure; Another question though: can buildbot be told not to build the > same revision twice (especially when it was succesful the first time)? Generaly the nightly task does just depend on the time. But I guess I can build a chain which does the checks, when I get the time. --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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Dennis Schridde schreef: > Am Donnerstag, 6. November 2008 01:08:31 schrieb [EMAIL PROTECTED]: >> 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/42 >> >> 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 shell_3 > "file exists" > > Can gpg be forced to create the signature? Not sure; Another question though: can buildbot be told not to build the same revision twice (especially when it was succesful the first time)? -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Donnerstag, 6. November 2008 01:08:31 schrieb [EMAIL PROTECTED]: > 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/42 > > 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 shell_3 "file exists" Can gpg be forced to create the signature? --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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Zarel schreef: > 2008/10/12 Giel van Schijndel <[EMAIL PROTECTED]>: >> Erm Why does it report failure? The build clearly succeeded... (i.e. >> [1] and [2] are produced as a result of it). >> >> [1] >> http://warzone.mortis.eu/nightly-builds/warzone2100-trunk-r6140-debug.exe >> [2] >> http://warzone.mortis.eu/nightly-builds/warzone2100-trunk-r6140-debug.exe.sig >> > > It appears that the debug build succeeded but the non-debug build failed. That buildbot doesn't build non-debug builds -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Montag, 13. Oktober 2008 12:34:06 schrieb Per Inge Mathisen: > On Mon, Oct 13, 2008 at 11:55 AM, Dennis Schridde <[EMAIL PROTECTED]> wrote: > > 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. > > What warning flags are used? http://build.kynes.de/builders/nightly_mingw32/builds/17/steps/configure/logs/stdio says debug=relaxed --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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
On Mon, Oct 13, 2008 at 11:55 AM, Dennis Schridde <[EMAIL PROTECTED]> wrote: > 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. What warning flags are used? - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
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
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
2008/10/12 Giel van Schijndel <[EMAIL PROTECTED]>: > Erm Why does it report failure? The build clearly succeeded... (i.e. > [1] and [2] are produced as a result of it). > > [1] > http://warzone.mortis.eu/nightly-builds/warzone2100-trunk-r6140-debug.exe > [2] > http://warzone.mortis.eu/nightly-builds/warzone2100-trunk-r6140-debug.exe.sig > It appears that the debug build succeeded but the non-debug build failed. -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
[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). [1] http://warzone.mortis.eu/nightly-builds/warzone2100-trunk-r6140-debug.exe [2] http://warzone.mortis.eu/nightly-builds/warzone2100-trunk-r6140-debug.exe.sig -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
[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/12 > > 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 configure Theora wasn't present yet in the devpkg. Fixed it. -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Dennis Schridde schreef: > Am Montag, 29. September 2008 02:07:12 schrieb [EMAIL PROTECTED]: >> 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/2 >> >> 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+100 > This was a *desired* failure. (In reality we have 505 warnings during builds > on the nightly node.) > Since everything seemed to work I am removing the hardcoded warningscount and > let it measure the warnings itself again. As interesting as these notices may be, could you please redirect these debug messages/mails to another e-mail address when you're just testing stuff out. -- Giel signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] buildbot failure in Warzone 2100: Resurrection Project on nightly_mingw32
Am Montag, 29. September 2008 02:07:12 schrieb [EMAIL PROTECTED]: > 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/2 > > 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+100 This was a *desired* failure. (In reality we have 505 warnings during builds on the nightly node.) Since everything seemed to work I am removing the hardcoded warningscount and let it measure the warnings itself again. --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
