aboutsummaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorFrank Lichtenheld <frank@lichtenheld.de>2007-05-27 14:33:09 +0200
committerJunio C Hamano <junkio@cox.net>2007-05-29 00:27:21 -0700
commitb3c81cff02e56a62bd657148da757fdfd8dc6255 (patch)
tree354eb08802d08748c0e1a66fa3c17686b4d0350a /t
parent2e4aef58932cdb345893103d77823a9dd6a146a6 (diff)
downloadgit-b3c81cff02e56a62bd657148da757fdfd8dc6255.tar.gz
git-b3c81cff02e56a62bd657148da757fdfd8dc6255.tar.xz
t9400: Work around CVS' deficiencies
If we are too fast with our changes, the file in the working copy might still have the same mtime as noted in the CVS/Entries. This will cause CVS to happily report to the server that the file is unmodified which can lead to data loss (and in our case test failure). CVS sucks! Work around that by sleeping for a second. Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 't')
-rwxr-xr-xt/t9400-git-cvsserver-server.sh2
1 files changed, 2 insertions, 0 deletions
diff --git a/t/t9400-git-cvsserver-server.sh b/t/t9400-git-cvsserver-server.sh
index 7f9c6e29b..76a9b1a5d 100755
--- a/t/t9400-git-cvsserver-server.sh
+++ b/t/t9400-git-cvsserver-server.sh
@@ -250,6 +250,7 @@ test_expect_success 'cvs update (merge)' \
git commit -q -m "Merge test (merge)" &&
git push gitcvs.git >/dev/null &&
cd cvswork &&
+ sleep 1 && touch merge &&
GIT_CONFIG="$git_config" cvs -Q update &&
diff -q merge ../expected'
@@ -292,6 +293,7 @@ test_expect_success 'cvs update (merge no-op)' \
git commit -q -m "Merge test (no-op)" &&
git push gitcvs.git >/dev/null &&
cd cvswork &&
+ sleep 1 && touch merge &&
GIT_CONFIG="$git_config" cvs -Q update &&
diff -q merge ../merge'