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/logging.sh | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'tests/logging.sh') diff --git a/tests/logging.sh b/tests/logging.sh index 0113ed11c..77b2337a9 100644 --- a/tests/logging.sh +++ b/tests/logging.sh @@ -3,7 +3,6 @@ source common.sh clearStore # Produce an escaped log file. -set -x path=$(nix-build --log-type escapes -vv dependencies.nix --no-out-link 2> $TEST_ROOT/log.esc) # Convert it to an XML representation. @@ -20,6 +19,6 @@ fi # Test compressed logs. clearStore rm -rf $NIX_LOG_DIR -! nix-store -l $path +(! nix-store -l $path) nix-build dependencies.nix --no-out-link --option build-compress-log true [ "$(nix-store -l $path)" = FOO ] -- cgit v1.2.3