git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>, git@vger.kernel.org
Subject: Re: testsuite problems
Date: Mon, 17 Sep 2007 23:40:27 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709172337470.28586@racer.site> (raw)
In-Reply-To: <20070917220408.GG19019@genesis.frugalware.org>

Hi,

On Tue, 18 Sep 2007, Miklos Vajna wrote:

> On Mon, Sep 17, 2007 at 11:50:32PM +0200, Ren? Scharfe <rene.scharfe@lsrfire.ath.cx> wrote:
> > The failing tests check ZIP file creation, not tar file creation.
> > Perhaps your unzip command works a bit differently from Info-ZIP's?
> 
> $ zip -v
> Copyright (c) 1990-2006 Info-ZIP - Type 'zip "-L"' for software license.
> This is Zip 2.32 (June 19th 2006), by Info-ZIP.
> 
> should this version be ok?
> 
> > 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)?
> 
> $ diff -Naur t/trash/a t/trash/d/a
> diff -Naur t/trash/a/l1 t/trash/d/a/l1
> --- t/trash/a/l1        2007-09-17 23:10:03.000000000 +0200
> +++ t/trash/d/a/l1      2007-09-17 23:10:03.000000000 +0200
> @@ -1 +1 @@
> -simple textfile
> +a
> \ No newline at end of file

Ah, that's my friend GNU diff again... Try running the test with "-i -v", 
and it will pass, if I am right.

I actually made a patch for GNU diff back when this hit me, only to find 
out that it was fixed in CVS.  Apparently, for a short period, during 
which 2.8.1 was released, there was a bug that prevented GNU diff from 
working properly when the output was redirected to a non-tty.

If I'm right, and it is that bug, it might be worthwhile to convert the 
calls to "diff -u" in that test script with calls to "git diff" (possibly 
with --no-index).

Ciao,
Dscho

  reply	other threads:[~2007-09-17 22:41 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
2007-09-17 22:04   ` Miklos Vajna
2007-09-17 22:40     ` Johannes Schindelin [this message]
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=Pine.LNX.4.64.0709172337470.28586@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=rene.scharfe@lsrfire.ath.cx \
    --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).