Use SIGABRT to kill stuck skrouterd, to get backtrace where it was stuck

[jiridanek]

Currently tests kill with sigkill. I am wondering if sigabrt would not be more appropriate.

skupper-router/tests/system_test.py

Lines 378 to 407 in 3111aaf

	if status is None:
	# The process is still running.
	# Call process.terminate() which will try to stop the child by sending it a SIGTERM
	# but is not guaranteed to stop it
	self.terminate()
	try:
	# Wait for TIMEOUT seconds and then catch the
	# TimeoutExpired and kill() the process.
	self.wait(timeout=TIMEOUT)
	except TimeoutExpired:
	# The terminate call() has failed to terminate the process even after we waited for TIMEOUT seconds.
	# Send a SIGKILL to the child by calling kill()
	self._logger.log("Wait timeout expired trying to terminate "
	"process %s (name=%s). Trying to kill process now" % (self.pid, self.name))
	self.kill()
	try:
	self.wait(timeout=TIMEOUT)
	self._logger.log("Process %s killed successfully" % self.pid)
	except TimeoutExpired:
	# There is something seriously wrong if kill() did not kill the process.
	# But should the test suite fail because of this ? Right now, it will
	# but we need to revisit this.
	error_msg = "Error: Could not kill process "
	self._logger.log(error_msg + self.pid)
	# This will raise a RuntimeError and fail the test
	error(error_msg)
	# At this time, we want to check if self.expect and self.actual are the same
	if self.expect != self.actual:
	error("exit code is %s, expected %s" % (self.actual, self.expect))

[jiridanek]

• Fixes #517 - Send SIGABRT to stuck subprocesses in test instead of SIGKILL #506