mirror of
https://github.com/fish-shell/fish-shell
synced 2025-01-13 21:44:16 +00:00
tests/invocation: Disable set -e
There's just waaayy too many things that could go wrong with it, so it annoys more than it helps, especially since we don't get any indication what failed. E.g. on FreeBSD, the test failed without a usable message just because `tput` couldn't find an attribute (so colors were unset).
This commit is contained in:
parent
6c1a2c1f30
commit
de32665939
1 changed files with 6 additions and 2 deletions
|
@ -54,8 +54,12 @@
|
|||
# non-zero.
|
||||
#
|
||||
|
||||
# Errors will be fatal
|
||||
set -e
|
||||
# With this, errors would be fatal.
|
||||
# However, a return value of non-zero doesn't signal something that necessarily should be fatal.
|
||||
# For instance, `tput` returns 1 if an attribute isn't defined.
|
||||
# But we don't want it to kill our script, especially not without any indication.
|
||||
#
|
||||
# set -e
|
||||
|
||||
# The directory this script is in (as everything is relative to here)
|
||||
here="$(cd "$(dirname "$0")" && pwd -P)"
|
||||
|
|
Loading…
Reference in a new issue