I left a gazebo simulation running in a docker container while running my overnight testing script. The INTEGRATION_world_clone test failed via timeout many times. Each time, the check_test_ran.py script found a rogue gzserver that had been cloned but not killed. Also, I saw the following console message:
473: sh: 1: kill: Operation not permitted
I believe that the Clone test doesn't get the correct process id when calling ps since it just takes the first one given to it. It would be more robust to try to identify which is the correct gzserver.
Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I left a gazebo simulation running in a docker container while running my overnight testing script. The
INTEGRATION_world_clone
test failed via timeout many times. Each time, thecheck_test_ran.py
script found a rogue gzserver that had been cloned but not killed. Also, I saw the following console message:I believe that the
Clone
test doesn't get the correct process id when calling ps since it just takes the first one given to it. It would be more robust to try to identify which is the correctgzserver
.