diff options
author | Junio C Hamano <gitster@pobox.com> | 2016-10-26 23:14:54 +0300 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2016-10-26 23:14:54 +0300 |
commit | f4db874d9adc3d974a085b1238aad0048e7f2674 (patch) | |
tree | 59fc5f6bb177ae3584510c4bd3bd3df604f8a9f5 /t/README | |
parent | bdcaebbedd54eeaf430ad1e4093a07922fe656d9 (diff) | |
parent | 614fe015212d057c0571885c42a29a995973107d (diff) |
Merge branch 'jk/tap-verbose-fix'
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/README | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -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 |