ctdb-tests: Don't run valgrind or other tracing in simple_test_command()
authorMartin Schwenke <martin@meltin.net>
Mon, 20 Aug 2018 04:55:17 +0000 (14:55 +1000)
committerAmitay Isaacs <amitay@samba.org>
Mon, 3 Sep 2018 12:04:00 +0000 (14:04 +0200)
commit30eb28818d5fbbb35d0965a92f721243aca6ab54
tree2fc53987b2d3baae0abeb693b623e6d1bf3973d0
parent8aacde3c5d86d8a0216b3bba200a39ca9a561653
ctdb-tests: Don't run valgrind or other tracing in simple_test_command()

This function is used to run a extra command to check a result.  This
command is usually a script (often a stub) or an external command, so
no need to trace it with valgrind or whatever else might be specified.
In the worst case the command being run is a shell function, which
valgrind won't be able to find.

There is little use running the event script tests under valgrind.
However, when the whole test suite is being run under valgrind then it
should work.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
Autobuild-User(master): Amitay Isaacs <amitay@samba.org>
Autobuild-Date(master): Mon Sep  3 14:04:00 CEST 2018 on sn-devel-144
ctdb/tests/eventscripts/scripts/local.sh