embre 2012 10:59:58 UTC+2, stefano perticoni ha
scritto:
>
> Hi,
>
> We did some investigation and the error message ie the strange stack trace
> with the space under Jenkins 1472 is related to the integration of the
> profiling tool gperftool in our codebase:
>
> http:/
blem, seems like no one can give a hint on
>> what is causing it to randomly fail once a week.
>> We're running Jenkins 1.467.
>>
>> BR,
>>
>> /Janne
>>
>> Den fredagen den 31:e augusti 2012 kl. 14:15:05 UTC+2 skrev Stefano
>> Per
ul build.
Any idea?
Thank you very much for your help.
Regards,
Stefano
___
Ing. Stefano Perticoni
Super Computing Solutions s.r.l.
http://www.scsitaly.com
Via Parini 1, 40033 Casalecchio di Reno BO, Italy
mailto: s.pertic...@scsi
ul build.
Any idea?
Thank you very much for your help.
Regards,
Stefano
___
Ing. Stefano Perticoni
Super Computing Solutions s.r.l.
http://www.scsitaly.com
Via Parini 1, 40033 Casalecchio di Reno BO, Italy
mailto: s.pertic...@scsi
Dear Christoph,
We implemented your proposed solution via the Groovy Plugin and it worked
ok to test for success patterns after each build step.
Thank you very much ,
Regards,
Stefano
___
Ing. Stefano Perticoni
Super Computing Solutions s.r.l.
http