From: "Torsten Bögershausen" <tboegi@web.de>
To: normalperson@yhbt.net, git@vger.kernel.org
Cc: tboegi@web.de
Subject: [PATCH] t9143: do not fail when unhandled.log.gz is not created
Date: Thu, 09 Dec 2010 20:53:19 +0100 [thread overview]
Message-ID: <4D0133AF.40000@web.de> (raw)
Do not depend on internal implementation details of svn,
which right now uses perl to create a .gz file.
So this test case will even work in the future,
when svn changes its implementation.
Signed-off-by: Torsten Bögershausen <tboegi@web.de>
---
t/t9143-git-svn-gc.sh | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/t/t9143-git-svn-gc.sh b/t/t9143-git-svn-gc.sh
index 337ea59..4594e1a 100755
--- a/t/t9143-git-svn-gc.sh
+++ b/t/t9143-git-svn-gc.sh
@@ -37,13 +37,11 @@ test_expect_success 'git svn gc runs' 'git svn gc'
test_expect_success 'git svn index removed' '! test -f
.git/svn/refs/remotes/git-svn/index'
-if perl -MCompress::Zlib -e 0 2>/dev/null
+if test -r .git/svn/refs/remotes/git-svn/unhandled.log.gz
then
test_expect_success 'git svn gc produces a valid gzip file' '
gunzip .git/svn/refs/remotes/git-svn/unhandled.log.gz
'
-else
- say "# Perl Compress::Zlib unavailable, skipping gunzip test"
fi
test_expect_success 'git svn gc does not change unhandled.log files' '
--
1.6.6
next reply other threads:[~2010-12-09 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 19:53 Torsten Bögershausen [this message]
2010-12-09 21:31 ` [PATCH] t9143: do not fail when unhandled.log.gz is not created Eric Wong
2010-12-10 0:11 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2010-12-04 11:37 Torsten Bögershausen
2010-12-06 19:23 ` Eric Wong
2010-12-08 16:25 ` Torsten Bögershausen
2010-12-08 21:41 ` Eric Wong
2010-12-04 11:37 Torsten Bögershausen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0133AF.40000@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.