summaryrefslogtreecommitdiff
path: root/t/README
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-10-28 09:01:20 -0700
committerJunio C Hamano <gitster@pobox.com>2016-10-28 09:01:21 -0700
commitb943a213fe6740f64e2ce3fafebce453814115d9 (patch)
treeb6b0b30cb2e6e433a9928d880da32d045151c1a0 /t/README
parentdce97d6ec73cdb1011589f7260e602a87088939b (diff)
parent614fe015212d057c0571885c42a29a995973107d (diff)
downloadgit-b943a213fe6740f64e2ce3fafebce453814115d9.tar.gz
Merge branch 'jk/tap-verbose-fix' into maint
The Travis CI configuration we ship ran the tests with --verbose option but this risks non-TAP output that happens to be "ok" to be misinterpreted as TAP signalling a test that passed. This resulted in unnecessary failure. This has been corrected by introducing a new mode to run our tests in the test harness to send the verbose output separately to the log file. * jk/tap-verbose-fix: test-lib: bail out when "-v" used under "prove" travis: use --verbose-log test option test-lib: add --verbose-log option test-lib: handle TEST_OUTPUT_DIRECTORY with spaces
Diffstat (limited to 't/README')
-rw-r--r--t/README6
1 files changed, 6 insertions, 0 deletions
diff --git a/t/README b/t/README
index 0f764c0aef..4982d1c521 100644
--- a/t/README
+++ b/t/README
@@ -153,6 +153,12 @@ appropriately before running "make".
As the names depend on the tests' file names, it is safe to
run the tests with this option in parallel.
+--verbose-log::
+ Write verbose output to the same logfile as `--tee`, but do
+ _not_ write it to stdout. Unlike `--tee --verbose`, this option
+ is safe to use when stdout is being consumed by a TAP parser
+ like `prove`. Implies `--tee` and `--verbose`.
+
--with-dashes::
By default tests are run without dashed forms of
commands (like git-commit) in the PATH (it only uses