From 3f80060500bb3a9dff192c11af63da7364673ab0 Mon Sep 17 00:00:00 2001
From: Eelco Dolstra <eelco.dolstra@logicblox.com>
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/case-hack.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'tests/case-hack.sh')

diff --git a/tests/case-hack.sh b/tests/case-hack.sh
index ebc7cb1d5..61bf9b94b 100644
--- a/tests/case-hack.sh
+++ b/tests/case-hack.sh
@@ -16,4 +16,4 @@ cmp case.nar $TEST_ROOT/case.nar
 # Check whether we detect true collisions (e.g. those remaining after
 # removal of the suffix).
 touch "$TEST_ROOT/case/xt_CONNMARK.h~nix~case~hack~3"
-! nix-store $opts --dump $TEST_ROOT/case > /dev/null
+(! nix-store $opts --dump $TEST_ROOT/case > /dev/null)
-- 
cgit v1.2.3