Thomas Haller f29aee87ec nmtst/valgrind: allow calling 'run-test-valgrind.sh' script directly ... When you want to run valgrind for a test, you either had to invoke valgrind manually, or doing it via `make check` (provided you configured --with-valgrind). Make it more convenient to run valgrind by passing the test to run to the "run-test-valgrind.sh" wrapper. This also allows to pass -p/-s to the test, which is not possible during `make check` because selecting tests conflicts with "--tap". The following invocations are largely equivalent and work as expected: $ ./tools/run-test-valgrind.sh ./src/platform/tests/test-link-linux -p /link/software/detect/vlan $ NMTST_DEBUG=no-debug,p=/link/software/detect/vlan ./tools/run-test-valgrind.sh ./src/platform/tests/test-link-linux (cherry picked from commit 4dacf0b1ad)		2015-11-24 11:14:50 +01:00
..
check-exports.sh	tools/check-exports.sh: use ${NM} when available	2015-09-24 16:33:12 +02:00
debug-helper.py	tools: move debug-helper.py from test/ to tools/	2014-07-30 15:56:19 -04:00
doc-generator.xsl	add tools directory and xsl for spec generation	2008-03-24 16:47:39 +00:00
Makefile.am	tools: move libnm-glib's fake NM service implementations here	2014-07-30 15:56:29 -04:00
run-test-valgrind.sh	nmtst/valgrind: allow calling 'run-test-valgrind.sh' script directly	2015-11-24 11:14:50 +01:00
test-networkmanager-service.py	tests: avoid calling GLib.IOChannel.unix_new()	2015-06-18 12:11:37 +02:00
test-sudo-wrapper.sh	nmtst: add nmtst_reexec_sudo() function	2014-06-05 18:12:57 +02:00