From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: testsuite problems
Date: Mon, 17 Sep 2007 23:50:32 +0200 [thread overview]
Message-ID: <46EEF6A8.1030308@lsrfire.ath.cx> (raw)
In-Reply-To: <20070917211742.GF19019@genesis.frugalware.org>
Miklos Vajna schrieb:
> * ok 18: git archive --format=zip
> * ok 19: extract ZIP archive
> * ok 20: validate filenames
> * FAIL 21: validate file contents
> diff -r a d/a
> * ok 22: git archive --format=zip with prefix
> * ok 23: extract ZIP archive with prefix
> * ok 24: validate filenames with prefix
> * FAIL 25: validate file contents with prefix
> diff -r a e/prefix/a
> * ok 26: git archive --list outside of a git repo
> * failed 2 among 26 test(s)
> make[1]: *** [t5000-tar-tree.sh] Error 1
> make[1]: Leaving directory `/home/vmiklos/git/git/t'
> make: *** [test] Error 2
>
> $ tar --version
> tar (GNU tar) 1.18
>
> $ diff --version
> diff (GNU diffutils) 2.8.1
>
> maybe these versions are too new or old? if i missed any needed info,
> please let me know.
The failing tests check ZIP file creation, not tar file creation.
Perhaps your unzip command works a bit differently from Info-ZIP's?
Also, what is the difference between t/trash/a and t/trash/d/a after
running the test script (that's what test 21 is comparing)?
René
next prev parent reply other threads:[~2007-09-17 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 21:17 testsuite problems Miklos Vajna
2007-09-17 21:41 ` Pierre Habouzit
2007-09-17 21:50 ` René Scharfe [this message]
2007-09-17 22:04 ` Miklos Vajna
2007-09-17 22:40 ` Johannes Schindelin
2007-09-17 22:48 ` Miklos Vajna
2007-09-17 22:50 ` Johannes Schindelin
2007-09-18 14:57 ` René Scharfe
2007-09-18 15:52 ` Miklos Vajna
2007-09-18 17:05 ` René Scharfe
2007-09-18 19:35 ` Miklos Vajna
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=46EEF6A8.1030308@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).