Ok we traced the issue: it was not a Jenkins one but a gperftool multi
thread profiling issue.
http://code.google.com/p/gperftools/?redir=1
We're switching to Valgrind (gperftool seems quite dead anyway...)
Thank you very much for your help,
Regards,
Stefano
Il giorno lunedì 3 settembre 201
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://code.google.com/p/gperftools/?redir=1
By disabling it the dashboard runs succesfully.
We just
The build is not failing because Jenkins can't delete the file. It's
failing (and the file can't be deleted) because the slave's network
connection to Jenkins was broken.
On Fri, Aug 31, 2012 at 6:30 PM, Richard J wrote:
> I see the same problem when running a "Windows batch file" type build ste
I see the same problem when running a "Windows batch file" type build step
on Windows slaves.
Maybe 1 out of 100 runs.
There was talk about this a year ago, but it was claimed to be fixed. (I
see it in ver 1.466.1)
On Friday, August 31, 2012 5:56:59 AM UTC-7, JanneG wrote:
> We're experienci
ssing, since I don't see
any obvious reasons for the issue).
Mark Waite
>
> From: JanneG
>To: jenkinsci-users@googlegroups.com
>Sent: Friday, August 31, 2012 6:56 AM
>Subject: Re: Build failing because Jenkins is unable to delete a tmp file
>
We're experiencing the same problem, 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
Perticoni:
>
> Dear Jenkins users,
>
> we are running Jenkins 1
Dear Jenkins users,
we are running Jenkins 1.472
http://scs03.cineca.it:9090/about/?
and we are experiencing this strange error from some time on a linux build
node:
http://scs03.cineca.it:9090/job/SCSSVN01_CI_LIB_MAF3_GCCDBG/:
Error first line:
30-Aug-2012 11:50:56 ---> Debug: ("mafPluginOutF
