t: document 'test_must_fail ok=<signal-name>'
Since 'test_might_fail' is implemented as a thin wrapper around 'test_must_fail', it also accepts the same options. Mention this in the docs as well. Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
fc849d8d6b
commit
12e31a6b12
@ -610,6 +610,14 @@ list_contains () {
|
||||
#
|
||||
# Writing this as "! git checkout ../outerspace" is wrong, because
|
||||
# the failure could be due to a segv. We want a controlled failure.
|
||||
#
|
||||
# Accepts the following options:
|
||||
#
|
||||
# ok=<signal-name>[,<...>]:
|
||||
# Don't treat an exit caused by the given signal as error.
|
||||
# Multiple signals can be specified as a comma separated list.
|
||||
# Currently recognized signal names are: sigpipe, success.
|
||||
# (Don't use 'success', use 'test_might_fail' instead.)
|
||||
|
||||
test_must_fail () {
|
||||
case "$1" in
|
||||
@ -656,6 +664,8 @@ test_must_fail () {
|
||||
#
|
||||
# Writing "git config --unset all.configuration || :" would be wrong,
|
||||
# because we want to notice if it fails due to segv.
|
||||
#
|
||||
# Accepts the same options as test_must_fail.
|
||||
|
||||
test_might_fail () {
|
||||
test_must_fail ok=success "$@"
|
||||
|
Reference in New Issue
Block a user