From: Mark Andrews <marka@isc.org>
Date: Fri, 14 Apr 2023 05:40:02 +0000 (+1000)
Subject: Use SIGABRT rather than SIGKILL for long running unit test
X-Git-Tag: v9.19.13~36^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=21a3d4f7623a3a2451554b900bd813de7cf7eddb;p=thirdparty%2Fbind9.git

Use SIGABRT rather than SIGKILL for long running unit test

SIGABRT will produce a core dump which will allow for forensic
analysis of the unit test
---

diff --git a/tests/unit-test-driver.sh.in b/tests/unit-test-driver.sh.in
index 68a0dcdfd62..9a60db1337b 100644
--- a/tests/unit-test-driver.sh.in
+++ b/tests/unit-test-driver.sh.in
@@ -35,8 +35,8 @@ while [ ${TIMEOUT} -gt 0 ]; do
 	TIMEOUT=$((TIMEOUT - 1))
 done
 if [ ${TIMEOUT} -eq 0 ]; then
-	echo "PID ${TEST_PROGRAM_PID} exceeded run time limit, sending SIGKILL" >&2
-	kill -KILL "${TEST_PROGRAM_PID}" 2>/dev/null
+	echo "PID ${TEST_PROGRAM_PID} exceeded run time limit, sending SIGABRT" >&2
+	kill -ABRT "${TEST_PROGRAM_PID}" 2>/dev/null
 fi
 
 TEST_PROGRAM_NAME=$(basename "${TEST_PROGRAM}")