Enable Valgrind support in the API suite
authorPetri Lehtinen <petri@digip.org>
Sun, 10 Jan 2010 14:18:45 +0000 (16:18 +0200)
committerPetri Lehtinen <petri@digip.org>
Sun, 10 Jan 2010 14:18:46 +0000 (16:18 +0200)
It was accidentally left out when the test system was refactored.

test/scripts/valgrind.sh
test/suites/api/run

index 7c23c79..39cda0d 100644 (file)
@@ -8,7 +8,10 @@
 VALGRIND_CMDLINE="valgrind --leak-check=full --show-reachable=yes --track-origins=yes -q"
 
 if [ $VALGRIND -eq 1 ]; then
 VALGRIND_CMDLINE="valgrind --leak-check=full --show-reachable=yes --track-origins=yes -q"
 
 if [ $VALGRIND -eq 1 ]; then
+    test_runner="$VALGRIND_CMDLINE"
     json_process="$VALGRIND_CMDLINE $json_process"
     json_process="$VALGRIND_CMDLINE $json_process"
+else
+    test_runner=""
 fi
 
 valgrind_check() {
 fi
 
 valgrind_check() {
index fbee1da..02e92b0 100755 (executable)
@@ -15,7 +15,10 @@ run_test() {
     if [ -x $test_path ]; then
         test_log=$test_log $test_path >$test_log/stdout 2>$test_log/stderr
     else
     if [ -x $test_path ]; then
         test_log=$test_log $test_path >$test_log/stdout 2>$test_log/stderr
     else
-        $suite_builddir/${test_name%.c} >$test_log/stdout 2>$test_log/stderr
+        $test_runner $suite_builddir/${test_name%.c} \
+            >$test_log/stdout \
+            2>$test_log/stderr
+        valgrind_check $test_log/stderr || return 1
     fi
 }
 
     fi
 }