From: Martin Schwenke Date: Tue, 21 Apr 2020 01:34:12 +0000 (+1000) Subject: ctdb-tests: Show hung script debugging output X-Git-Tag: talloc-2.3.2~1019 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1565446508fcf2bdd1ae9c39cc3822417cd91dc8;p=thirdparty%2Fsamba.git 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 Reviewed-by: Amitay Isaacs --- 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