#751: Sending SIGTERM before SIGKILL to a remote shell command that has timed
out
------------------------+---------------------------------------------------
Reporter: Fabrice | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: undecided
Version: 0.7.12 | Keywords:
------------------------+---------------------------------------------------
I have a test step that does not produce output for one hour (the test or
one of its subtest hangs for some reason). My buildbot is configured to
timeout this step/command after 3600 seconds of inactivity on stdout or
stderr. Thus buildbot sends correctly, as expected, a signal SIGKILL(9) to
it and writes in the log:
{{{
command timed out: 3600 seconds without output, killing pid <PID>
process killed by signal 9
}}}
However, my problem is the following. There is no way for me to catch/trap
SIGKILL(9) in my test step process running on the slave and thus, I am
missing test logs. Is it possible to make buildbot send a couple of
SIGTERM(15) signals before sending a SIGKILL(9) signal?
--
Ticket URL: <http://buildbot.net/trac/ticket/751>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
