git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git <git@vger.kernel.org>
Subject: Re: cogito testsuite failure
Date: Wed, 01 Jun 2005 01:34:09 -0400	[thread overview]
Message-ID: <1117604049.5755.3.camel@dv> (raw)
In-Reply-To: <7vzmuasnui.fsf@assigned-by-dhcp.cox.net>

Hi, Junio!

On Tue, 2005-05-31 at 21:27 -0700, Junio C Hamano wrote:
> My intention was not to check the actual SHA1 in anything other
> than t0000-basic.sh, but some test in t4000 series were buggy
> and ended up comparing the SHA1.
> 
> I have since corrected them and I believe the test suite in the
> current tip of Linus tree has the corrected compare_diff_raw and
> friends in t/diff-lib.sh, which t4000 series use to avoid this
> problem.  I just hand munged COPYING and README and ran t4008 in
> the Linus tree, and do not see the problem you are reporting.
> 
> Could you verify that your test failure is coming from the
> version that was before t/diff-lib.sh was introduced?  Otherwise
> I have to investigate this further.

The failure in on the "cogito" branch
(rsync://rsync.kernel.org/pub/scm/cogito/cogito.git), which doesn't have
t/diff-lib.sh.

The "git" branch (rsync://www.kernel.org/pub/scm/git/git.git) is fine.
Sorry for the noise.  I should have checked that branch too.

-- 
Regards,
Pavel Roskin


  reply	other threads:[~2005-06-01  5:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01  3:47 cogito testsuite failure Pavel Roskin
2005-06-01  4:27 ` Junio C Hamano
2005-06-01  5:34   ` Pavel Roskin [this message]
2005-06-01  5:55     ` Junio C Hamano

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=1117604049.5755.3.camel@dv \
    --to=proski@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.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 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).