SZEDER Gábor 677c70799c travis-ci: only print test failures if there are test results available ... When a build job running the test suite fails, our 'ci/print-test-failures.sh' script scans all 't/test-results/*.exit' files to find failed tests and prints their verbose output. However, if a build job were to fail before it ever gets to run the test suite, then there will be no files to match the above pattern and the shell will take the pattern literally, resulting in errors like this in the trace log: cat: t/test-results/*.exit: No such file or directory ------------------------------------------------------------------------ t/test-results/*.out... ------------------------------------------------------------------------ cat: t/test-results/*.out: No such file or directory Check upfront and proceed only if there are any such files present. Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com> Reviewed-by: Lars Schneider <larsxschneider@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>		2017-12-27 12:15:22 -08:00
..
install-dependencies.sh
lib-travisci.sh	travis-ci: fine tune the use of 'set -x' in 'ci/*' scripts	2017-12-27 12:13:46 -08:00
print-test-failures.sh	travis-ci: only print test failures if there are test results available	2017-12-27 12:15:22 -08:00
run-build.sh
run-linux32-build.sh	travis-ci: save prove state for the 32 bit Linux build	2017-12-27 12:15:05 -08:00
run-linux32-docker.sh	travis-ci: save prove state for the 32 bit Linux build	2017-12-27 12:15:05 -08:00
run-static-analysis.sh
run-tests.sh
run-windows-build.sh	travis-ci: fine tune the use of 'set -x' in 'ci/*' scripts	2017-12-27 12:13:46 -08:00
test-documentation.sh