summaryrefslogtreecommitdiff
path: root/t/t4104-apply-boundary.sh
diff options
context:
space:
mode:
authorLibravatar Jens Lehmann <Jens.Lehmann@web.de>2011-07-24 15:35:54 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-07-24 11:55:14 -0700
commit2579e1d2936ad4e385ef21e5c346d9853d7faa01 (patch)
tree1fdf14944bf939bb34885d52d411badb61d70f74 /t/t4104-apply-boundary.sh
parentdoc/fast-import: clarify notemodify command (diff)
downloadtgif-2579e1d2936ad4e385ef21e5c346d9853d7faa01.tar.xz
tests: print failed test numbers at the end of the test run
On modern multi-core processors "make test" is often run in multiple jobs. If one of them fails the test run does stop, but the concurrently running tests finish their run. It is rather easy to find out which test failed by doing a "ls -d t/trash*". But that only works when you don't use the "-i" option to "make test" because you want to get an overview of all failing tests. In that case all thrash directories are deleted end and the information which tests failed is lost. If one or more tests failed, print a list of them before the test summary: failed test(s): t1000 t6500 fixed 0 success 7638 failed 3 broken 49 total 7723 This makes it possible to just run the test suite with -i and collect all failed test scripts at the end for further examination. Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4104-apply-boundary.sh')
0 files changed, 0 insertions, 0 deletions