summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2020-04-21 11:34:12 +1000
committerMartin Schwenke <martins@samba.org>2020-07-22 07:53:35 +0000
commit1565446508fcf2bdd1ae9c39cc3822417cd91dc8 (patch)
tree2bccc3eeca285979f0a8c88e1dc8cadf87f596bd
parent70c38d404b480c0b63621bd1faf002485faac531 (diff)
downloadsamba-1565446508fcf2bdd1ae9c39cc3822417cd91dc8.tar.gz
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>
-rwxr-xr-xctdb/tests/INTEGRATION/simple/eventscripts.090.debug_hung.sh5
1 files changed, 5 insertions, 0 deletions
diff --git a/ctdb/tests/INTEGRATION/simple/eventscripts.090.debug_hung.sh b/ctdb/tests/INTEGRATION/simple/eventscripts.090.debug_hung.sh
index e77c3987bc8..0e39496155e 100755
--- 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