-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
This is on:
hudson@wssqe27 /proc $ uname -a
SunOS wssqe27 5.11 snv_70b sun4u sparc SUNW,Sun-Blade-1500
pargs -e shows it has the cookie:
hudson@wssqe27 /proc $ pargs -e 6107
6107: /files/hudson/tools/native/java1.6.0_06/bin/java -cp
/files/hudson/workspace/SQ
...
envp[9]: HUDSON_COOKIE=f200d29d-19cf-4b01-833d-63bc8c5c1a1c
...
Perhaps the killer doesn't work on Sparc?
[JENKINS-2729] Hudson failed to kill run-away GF?
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JNJira [ 132802 ] | New: JNJira + In-Review [ 201676 ] |
Adding Sudipa to the CC list.
After more investigation, the killer seems to be working correctly.
The issue now seems to be that if a build succeeds but leave a daemon behind,
Hudson won't notice.
So the question is, whether I should kill run-away processes or not. Maybe the
daemon process forked from a build is intentional, which makes this hard...