Don't use a Unix signal handler to kill the test-application if the parent test program aborts

This is super sketchy; moreover, we can rely on the test runner to
kill child processes.

2 files changed, 0 insertions, 14 deletions

diff --git a/tests/at-spi2-atk/atk_suite.c b/tests/at-spi2-atk/atk_suite.c
index f70e8cb8..02f85917 100644
--- a/tests/at-spi2-atk/atk_suite.c
+++ b/tests/at-spi2-atk/atk_suite.c
@@ -55,8 +55,6 @@ main (int argc, char **argv)
 {
   g_test_init (&argc, &argv, NULL);
 
-  clean_exit_on_fail ();
-
   atk_suite_build ();
 
   return g_test_run ();
diff --git a/tests/at-spi2-atk/atk_test_util.c b/tests/at-spi2-atk/atk_test_util.c
index a56b7913..b22aa3f6 100644
--- a/tests/at-spi2-atk/atk_test_util.c
+++ b/tests/at-spi2-atk/atk_test_util.c
@@ -26,18 +26,6 @@
 static pid_t child_pid;
 
 static void
-assert_clean_exit (int sig)
-{
-  kill (child_pid, SIGTERM);
-}
-
-void
-clean_exit_on_fail ()
-{
-  signal (SIGABRT, assert_clean_exit);
-}
-
-static void
 run_app (const char *file_name)
 {
   child_pid = fork ();