git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Habouzit <madcoder@debian.org>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: testsuite problems
Date: Mon, 17 Sep 2007 23:41:03 +0200	[thread overview]
Message-ID: <20070917214103.GA13298@artemis.corp> (raw)
In-Reply-To: <20070917211742.GF19019@genesis.frugalware.org>

[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]

On Mon, Sep 17, 2007 at 09:17:42PM +0000, Miklos Vajna wrote:
> hello,
> 
> i was running 'make test' on v1.5.3.1-109-gacd6917 and i hit the
> following issue:
> 
[...]
> * 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

  Well, it works for me:

$ git describe && git st
v1.5.3.1-109-gacd6917
# Not currently on any branch.
nothing to commit (working directory clean)

$ cd t && ./t5000-tar-tree.sh
*   ok 1: populate workdir
*   ok 2: add files to repository
*   ok 3: git archive
*   ok 4: git tar-tree
*   ok 5: git archive vs. git tar-tree
*   ok 6: validate file modification time
*   ok 7: git get-tar-commit-id
*   ok 8: extract tar archive
*   ok 9: validate filenames
*   ok 10: validate file contents
*   ok 11: git tar-tree with prefix
*   ok 12: extract tar archive with prefix
*   ok 13: validate filenames with prefix
*   ok 14: validate file contents with prefix
*   ok 15: create an archive with a substfile
*   ok 16: extract substfile
*   ok 17: validate substfile contents
*   ok 18: git archive --format=zip
*   ok 19: extract ZIP archive
*   ok 20: validate filenames
*   ok 21: validate file contents
*   ok 22: git archive --format=zip with prefix
*   ok 23: extract ZIP archive with prefix
*   ok 24: validate filenames with prefix
*   ok 25: validate file contents with prefix
*   ok 26: git archive --list outside of a git repo
* passed all 26 test(s)

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-09-17 21:42 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 [this message]
2007-09-17 21:50 ` René Scharfe
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=20070917214103.GA13298@artemis.corp \
    --to=madcoder@debian.org \
    --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).