summaryrefslogtreecommitdiff
path: root/t/t5800-remote-testpy.sh
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-01-14 08:15:46 -0800
committerJunio C Hamano <gitster@pobox.com>2013-01-14 08:15:46 -0800
commit6f3f710127b0d5b651915b705a18a25e389fd40d (patch)
treeb800a446e261e4379d14456b7a6dd7439c27d4c3 /t/t5800-remote-testpy.sh
parente43171a4a728f627aed7a7b4682e6da2cb378253 (diff)
parent6c323322682abed3bb2a3904596b529ebccddb1c (diff)
downloadgit-6f3f710127b0d5b651915b705a18a25e389fd40d.tar.gz
Merge branch 'fc/remote-testgit-feature-done'
In the longer term, tightening rules is a good thing to do, and because nobody who has worked in the remote helper area seems to be interested in reviewing this, I would assume they do not think such a retroactive tightening will affect their remote helpers. So let's advance this topic to see what happens. * fc/remote-testgit-feature-done: remote-testgit: properly check for errors
Diffstat (limited to 't/t5800-remote-testpy.sh')
-rwxr-xr-xt/t5800-remote-testpy.sh21
1 files changed, 21 insertions, 0 deletions
diff --git a/t/t5800-remote-testpy.sh b/t/t5800-remote-testpy.sh
index 6750961507..1e683d4220 100755
--- a/t/t5800-remote-testpy.sh
+++ b/t/t5800-remote-testpy.sh
@@ -145,4 +145,25 @@ test_expect_failure 'push new branch with old:new refspec' '
compare_refs clone HEAD server refs/heads/new-refspec
'
+test_expect_success 'proper failure checks for fetching' '
+ (GIT_REMOTE_TESTGIT_FAILURE=1 &&
+ export GIT_REMOTE_TESTGIT_FAILURE &&
+ cd localclone &&
+ test_must_fail git fetch 2>&1 | \
+ grep "Error while running fast-import"
+ )
+'
+
+# We sleep to give fast-export a chance to catch the SIGPIPE
+test_expect_failure 'proper failure checks for pushing' '
+ (GIT_REMOTE_TESTGIT_FAILURE=1 &&
+ export GIT_REMOTE_TESTGIT_FAILURE &&
+ GIT_REMOTE_TESTGIT_SLEEPY=1 &&
+ export GIT_REMOTE_TESTGIT_SLEEPY &&
+ cd localclone &&
+ test_must_fail git push --all 2>&1 | \
+ grep "Error while running fast-export"
+ )
+'
+
test_done