m job is running.
>
> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] On Behalf Of Richard Bywater
> Sent: Friday, August 10, 2012 12:36 AM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: Immortal phantom buil
The weird thing is that all slaves were still working and I could build
other jobs, so if it's memory related issue, then it might affect that
particular phantom build.
The other problem is on identifying which slave is having the problem. I
checked the logs of each one, and didn't find any error.
m] On Behalf Of Richard Bywater
Sent: Friday, August 10, 2012 12:36 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Immortal phantom build
I think the last few times that's happened to me its been memory related (e.g.
out of PermGen). Think it spat some errors out to the Winstone wrappe
I think the last few times that's happened to me its been memory
related (e.g. out of PermGen). Think it spat some errors out to the
Winstone wrapper.log.
Possibly not related to your issue but just in case...
Cheers
Richard.
On Fri, Aug 10, 2012 at 11:44 AM, Cliffano Subagio wrote:
> Hi,
>
> O
Hi,
One of my Jenkins jobs is running (the job page showing a build in
progress), but the console output page only shows the spinning wheel
without anything else
On the dashboard page, none of the executors is running that job, all
executors on all slaves are idle.
I got the /threadDump output wh
