projects / git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9ff18fa) | patch
test_must_fail: report number of unexpected signal
authorJeff King <peff@peff.net>
Wed, 24 Feb 2016 07:45:49 +0000 (02:45 -0500)
committerJunio C Hamano <gitster@pobox.com>
Thu, 25 Feb 2016 21:51:47 +0000 (13:51 -0800)
commitf3ed0b372d990eade2e4727f17d9ee40003badb1
treeb5e469ecc9cc0ff511fb5ebd91433041808c7372tree | snapshot
parent9ff18faf2f8578ed1cbc4376b594fa7ff22c9085commit | diff
test_must_fail: report number of unexpected signal

If a command is marked as test_must_fail but dies with a
signal, we consider that a problem and report the error to
stderr. However, we don't say _which_ signal; knowing that
can make debugging easier. Let's share as much as we know.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/test-lib-functions.sh diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.