-
Bug
-
Resolution: Not A Defect
-
Major
-
Windows XP Professional, Version 2002, SP3
Intel(R)Xeon(R) CPU
X5670 @ 2.93 GHz
2,67 GHz, 2,00 GB of RAM
Physical Address Extension
The Jenkins build job is hanging since 4h (although a timeout of 3h was given), no log file exists, therefore I cannot see, at which action the job hangs. I only see the spinning wheel and the following information:
build has been executing for null on master.
I suppose the following:
The first build job was started on the Jenkins slave MU719161, setting up a clearcase view there. The next build jobs were also led to the same Jenkins slave, using this clearcase view. The hanging job seems to be executing on the Jenkins master, where this clearcase view does not exist. Now it is waiting for something forever.
I have changed the input parameters of the jobs such, that all execute on the Jenkins slave with the same label. The building was successfully.
However, how can I kill the hanging job? It does not react on stopping! I would like to avoid reboot of the Jenkins master.
Uploaded is a stacktrace taken on master with jstack and the treadDump from master (where I deleted all non relevant slaves)
Thank you very much for your help.