test: fix the valgrind test-case to not hang if valgrind crashes
authorNils Carlson <nils.carlson@ericsson.com>
Fri, 4 Mar 2011 15:08:39 +0000 (16:08 +0100)
committerNils Carlson <nils.carlson@ericsson.com>
Fri, 4 Mar 2011 15:47:53 +0000 (16:47 +0100)
In previous version of the test-case the test-case would hang forever
if valgrind crashes (which it does on my debian squeeze PPC).

Fix this by checking that valgrind is alive.

Also cleanup leftover fifos in /tmp

Signed-off-by: Nils Carlson <nils.carlson@ericsson.com>
tests/valgrind_ust-consumerd.sh

index 5b348d7825a5b01a2adc54cbb3d250c585dbdbe4..856808bb7d954ac2a5be4a4f64fd1814f76dc124 100755 (executable)
@@ -45,6 +45,14 @@ VALG_OUT=/tmp/ust-testsuite-$USER-valg.txt
 export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$TESTDIR/../libustconsumer/.libs/"
 valgrind --suppressions=$TESTDIR/valgrind_suppress.txt -q $UST_CONSUMERD --pidfile "$pidfilepath" -o "$TRACE_DIR" >/dev/null 2>"$VALG_OUT" &
 VALG_PID=$!
+
+# Paranoid check that valgrind is alive or we will hang forever on the fifo
+if ! ps $VALG_PID > /dev/null; then
+    echo "Valgrind appears to have died, giving up"
+    rm $pidfilepath
+    exit
+fi
+
 UST_CONSUMERD_PID="$(<$pidfilepath)"
 
 okx $USTTRACE -L -s $TESTDIR/basic/.libs/basic
@@ -61,3 +69,5 @@ else
        diag "$REPLY"
     done
 fi
+
+rm $pidfilepath
This page took 0.02538 seconds and 4 git commands to generate.