summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 6368d9f)
raw | patch | inline | side by side (parent: 6368d9f)
author | Carlos Martín Nieto <cmn@elego.de> | |
Tue, 15 Mar 2011 09:32:11 +0000 (10:32 +0100) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Mon, 21 Mar 2011 04:19:38 +0000 (21:19 -0700) |
The test suite runs valgrind with certain options activated. Add a
note saying how to run commands under the same conditions as the test
suite does.
Signed-off-by: Carlos Martín Nieto <cmn@elego.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
note saying how to run commands under the same conditions as the test
suite does.
Signed-off-by: Carlos Martín Nieto <cmn@elego.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/README | patch | blob | history |
diff --git a/t/README b/t/README
index 78c9e6575c8a1f1060aada39dc5043eea807ac1c..d44a614ea32cf83915098e91ec7be603a13cb6d6 100644 (file)
--- a/t/README
+++ b/t/README
not see any output, this option implies --verbose. For
convenience, it also implies --tee.
+ Note that valgrind is run with the option --leak-check=no,
+ as the git process is short-lived and some errors are not
+ interesting. In order to run a single command under the same
+ conditions manually, you should set GIT_VALGRIND to point to
+ the 't/valgrind/' directory and use the commands under
+ 't/valgrind/bin/'.
+
--tee::
In addition to printing the test output to the terminal,
write it to files named 't/test-results/$TEST_NAME.out'.