MantisBT - CMake
View Issue Details
0012038CMakeCTestpublic2011-04-03 17:302016-06-10 14:31
samuel nobs 
Kitware Robot 
normalfeaturealways
closedmoved 
CMake 2.8.4 
 
0012038: SIGKILL sent when process times out
when a test process times out, ctest sends a SIGSTOP followed by a SIGKILL to terminate the process. this is a bit harsh, since the process will not be able to clean up resources like lock files, hence making following test potentially fail when trying to acquire said resources.

it would be way more graceful to first send a SIGTERM, giving the process some time to reminate sensibly, and then send a SIGKILL after some time in case the process really insist on continuing to run
No tags attached.
Issue History
2011-04-03 17:30samuel nobsNew Issue
2011-04-03 18:23samuel nobsNote Added: 0026027
2011-04-04 10:32Brad KingAssigned To => Brad King
2011-04-04 10:32Brad KingStatusnew => assigned
2011-04-04 10:35Brad KingNote Added: 0026035
2011-04-04 10:35Brad KingAssigned ToBrad King =>
2011-04-04 10:35Brad KingStatusassigned => backlog
2016-06-10 14:28Kitware RobotNote Added: 0041827
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0026027)
samuel nobs   
2011-04-03 18:23   
or replace SIGKILL completely with SIGTERM (that's what i've done using a patch on my cmake checkout)
(0026035)
Brad King   
2011-04-04 10:35   
When a test times out that means it is misbehaving. The parent process wants it to just be gone.

Tests should be written to run with a state that is as local as possible so that it can always be reset when the tests start again.
(0041827)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.