From 3f80060500bb3a9dff192c11af63da7364673ab0 Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Thu, 21 Aug 2014 21:50:19 +0200 Subject: Fix tests So all these years I was totally deluded about the meaning of "set -e". You might think that it causes statements like "false && true" or "! true" to fail, but it doesn't... --- tests/lang.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tests/lang.sh') diff --git a/tests/lang.sh b/tests/lang.sh index 7157a68c5ceb..c797a2a74ed8 100644 --- a/tests/lang.sh +++ b/tests/lang.sh @@ -3,7 +3,7 @@ source common.sh export TEST_VAR=foo # for eval-okay-getenv.nix nix-instantiate --eval -E 'builtins.trace "Hello" 123' 2>&1 | grep -q Hello -! nix-instantiate --show-trace --eval -E 'builtins.addErrorContext "Hello" 123' 2>&1 | grep -q Hello +(! nix-instantiate --show-trace --eval -E 'builtins.addErrorContext "Hello" 123' 2>&1 | grep -q Hello) nix-instantiate --show-trace --eval -E 'builtins.addErrorContext "Hello" (throw "Foo")' 2>&1 | grep -q Hello set +x -- cgit 1.4.1