[Xen-changelog] Fix up non-valgrind case to send stderr to file like valgrind case does.

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User cl349@xxxxxxxxxxxxxxxxxxxx
# Node ID a2f9f958fb1404a0f6cb057fe5bf3fb5096effb0
# Parent  f9a8f24dac6784d097ad3fb0963e55947b1a219f
Fix up non-valgrind case to send stderr to file like valgrind case does.
(Having trouble with signal delivery and valgrind, causing spurious test
timeouts)
Signed-off-by: Rusty Russel <rusty@xxxxxxxxxxxxxxx>
Signed-off-by: Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>

diff -r f9a8f24dac67 -r a2f9f958fb14 tools/xenstore/testsuite/test.sh
--- a/tools/xenstore/testsuite/test.sh  Tue Aug  2 17:59:20 2005
+++ b/tools/xenstore/testsuite/test.sh  Tue Aug  2 17:59:59 2005
@@ -14,7 +14,10 @@
        PID=`cat /tmp/pid`
        rm /tmp/pid
     else
-       PID=`./xenstored_test --output-pid`
+       ./xenstored_test --output-pid --trace-file=testsuite/tmp/trace 
--no-fork > /tmp/pid 2> testsuite/tmp/xenstored_errors &
+       while [ ! -s /tmp/pid ]; do sleep 0; done
+       PID=`cat /tmp/pid`
+       rm /tmp/pid
     fi
     if sh -e $2 $1; then
        if [ -s testsuite/tmp/vgout ]; then

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog