[PATCH nbdkit] tests: Add -v (verbose) whenever we run nbdkit in test functions.
This enables debugging in the test output, and has no noticable effect (ie. all the tests still pass both without and with valgrind). Rich.
Getting full output from nbdkit is worthwhile when debugging tests. --- tests/functions.sh.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/functions.sh.in b/tests/functions.sh.in index 8c65884..d647639 100644 --- a/tests/functions.sh.in +++ b/tests/functions.sh.in @@ -72,7 +72,7 @@ start_nbdkit () pidfile="$2" # Run nbdkit. - nbdkit "$@" + nbdkit -v "$@" # Wait for the pidfile to appear. for i in {1..10}; do -- 2.19.0.rc0
On 12/1/18 5:09 PM, Richard W.M. Jones wrote:
Getting full output from nbdkit is worthwhile when debugging tests. --- tests/functions.sh.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
LGTM
diff --git a/tests/functions.sh.in b/tests/functions.sh.in index 8c65884..d647639 100644 --- a/tests/functions.sh.in +++ b/tests/functions.sh.in @@ -72,7 +72,7 @@ start_nbdkit () pidfile="$2"
# Run nbdkit. - nbdkit "$@" + nbdkit -v "$@"
# Wait for the pidfile to appear. for i in {1..10}; do
-- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
participants (2)
-
Eric Blake -
Richard W.M. Jones