diff options
| author | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2014-08-21T19·50+0200 |
|---|---|---|
| committer | Eelco Dolstra <eelco.dolstra@logicblox.com> | 2014-08-21T19·50+0200 |
| commit | 3f80060500bb3a9dff192c11af63da7364673ab0 (patch) | |
| tree | 49aa943001a44d1db7f5fdb1e87d15f55f67bfa3 /tests/gc-concurrent.sh | |
| parent | 809ca33806d75eeabb9c668b124762fb6462e5bc (diff) | |
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...
Diffstat (limited to 'tests/gc-concurrent.sh')
| -rw-r--r-- | tests/gc-concurrent.sh | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/tests/gc-concurrent.sh b/tests/gc-concurrent.sh index 0bc5a12d31..d395930ca0 100644 --- a/tests/gc-concurrent.sh +++ b/tests/gc-concurrent.sh @@ -11,7 +11,7 @@ outPath2=$(nix-store -q $drvPath2) drvPath3=$(nix-instantiate simple.nix) outPath3=$(nix-store -r $drvPath3) -! test -e $outPath3.lock +(! test -e $outPath3.lock) touch $outPath3.lock rm -f "$NIX_STATE_DIR"/gcroots/foo* @@ -50,9 +50,9 @@ rm -f "$NIX_STATE_DIR"/gcroots/foo* # The collector should have deleted lock files for paths that have # been built previously. -! test -e $outPath3.lock +(! test -e $outPath3.lock) # If we run the collector now, it should delete outPath1/2. nix-collect-garbage -! test -e $outPath1 -! test -e $outPath2 +(! test -e $outPath1) +(! test -e $outPath2) |