Don't use test_expect_failure when more than one thing could fail

It's much better to use ! for the part that you actually expect to
fail; that way, the test will still scream if something _else_ goes
wrong.

Signed-off-by: Karl Hasselström <kha@treskal.com>

diff --git a/t/t2101-pull-policy-pull.sh b/t/t2101-pull-policy-pull.sh
index 793491c890d17f2471b5786ec712b2100f8f52be..14d5adb7a378d484df5d577d09d7e9dd06d3c309 100755 (executable)
--- a/t/t2101-pull-policy-pull.sh
+++ b/t/t2101-pull-policy-pull.sh
@@ -39,11 +39,11 @@ test_expect_success \
 # as rewinding, and thus heads/origin is not moved, but the stack
 # is still correctly rebased
 
 # as rewinding, and thus heads/origin is not moved, but the stack
 # is still correctly rebased
 

-test_expect_failure \
+test_expect_success \

     'Rewind/rewrite upstream commit and pull it from clone, without --merged' \
     '
     (cd upstream && echo b >> file2 && stg refresh) &&
     'Rewind/rewrite upstream commit and pull it from clone, without --merged' \
     '
     (cd upstream && echo b >> file2 && stg refresh) &&

-    (cd clone && stg pull)
+    (cd clone && ! stg pull)

     '
 
 test_expect_success \
     '
 
 test_expect_success \