ctdb-tests: Show hung script debugging output

The output in a test failure appears to contain no pstree output
because "00\.test\.script,.*" does not match.  However, this is just a
guess because the output is not shown.

Showing the output makes it easier to understand test failures.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>

diff --git a/ctdb/tests/INTEGRATION/simple/eventscripts.090.debug_hung.sh b/ctdb/tests/INTEGRATION/simple/eventscripts.090.debug_hung.sh
index e77c3987bc8e90b8be5f2d1191e6eb5b76720d34..0e39496155e34c0d065a5e6ee96ec9d966fd446c 100755 (executable)
--- a/ctdb/tests/INTEGRATION/simple/eventscripts.090.debug_hung.sh
+++ b/ctdb/tests/INTEGRATION/simple/eventscripts.090.debug_hung.sh
@@ -53,6 +53,11 @@ echo "Waiting for debugging output to appear..."
 # Use test -s because the file is created above using mktemp
 wait_until 60 test -s "$debug_output"
 
+echo
+echo "Debugging output:"
+cat "$debug_output"
+echo
+
 echo "Checking output of hung script debugging..."
 
 # Can we actually read kernel stacks