Bug 8268

Summary: Killing bitbake with SIGKILL does not always kill child processes.
Product: [Build System, Metadata & Runtime] BitBake Reporter: Beth Flanagan <elizabeth.flanagan>
Component: bitbakeAssignee: Richard Purdie <richard.purdie>
Status: VERIFIED FIXED QA Contact: Mihail Stanciu <stanciux.mihail>
Severity: normal    
Priority: High CC: bogdanx.a.voiculescu, poky.bs.watcher, poky.watcher
Version: unspecified   
Target Milestone: 1.9 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Beth Flanagan 2015-09-08 11:37:14 UTC
From:

https://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/492

This build was interrupted by buildbot (SIGKILL) however processes are still hanging about:

[eflanagan@fedora21 ~]$ ps aux|grep bitbake
pokybui+  2345  0.0  0.0 217836  2400 ?        SNs  Sep04   0:05 python /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/bitbake/bin/bitbake-worker decafbad
pokybui+  2724  0.0  0.0 205440  2400 ?        SNs  Sep04   0:00 python /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/bitbake/bin/bitbake-worker decafbad
eflanag+  7005  0.0  0.0 113004  2340 pts/2    S+   11:26   0:00 grep --color=auto bitbake
pokybui+  8454  0.0  0.0 430820  3116 ?        SNs  Sep04   0:06 python /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-x86-64/build/bitbake/bin/bitbake-worker decafbad

I would think that this isn't an autobuilder issue as the autobuilder is reporting:

command interrupted, attempting to kill
process killed by signal 9
program finished with exit code -1
elapsedTime=4928.831333

So autobuilder is picking up that it killed the parent process but it seems some of the children are still about.
Comment 2 Mihail Stanciu 2015-09-18 14:07:48 UTC
Verified on master: ea562de57590c966cd5a75fda8defecd397e6436