[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Build failed in Jenkins: gnustep #255

From: Gregory Casamento
Subject: Re: Build failed in Jenkins: gnustep #255
Date: Thu, 9 Aug 2012 20:58:57 -0400

Given that this has happened rarely, I don't see your point in saying "yet another."

The correct course of action is to improve the build system, not to ignore it. 

I'm beginning to be seriously disheartened by the reaction of the community to using Jenkins.  The fact of the matter is that in over 250+ builds sinc it started it has reported a false error three times which is not a bad reliability factor.   

The above assertion is observable by going to the site I have set up and looking at the statistics for yourself.

Given this your exasperation confuses me. 


On Thursday, August 9, 2012, Wolfgang Lux wrote:
Am 09.08.2012 um 21:13 schrieb address@hidden:

> See <>
> [...]
> obj/GormCore.obj/GormViewWindow.m.d:1: warning: NUL character seen; rest of line ignored
> obj/GormCore.obj/GormViewWindow.m.d:1: *** missing separator.  Stop.
> make[2]: *** [GormCore.all.library.variables] Error 2
> make[1]: *** [internal-all] Error 2
> make[1]: Leaving directory `<'>
> make: *** [internal-all] Error 2
> Build step 'Execute shell' marked build as failure

Yet another error due to a broken build system. I start considering a filter which moves emails with subject 'Build failed in Jenkins' directly to the trash.


Gregory Casamento
Open Logic Corporation, Principal Consultant
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]