git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.2.2
Date: Mon, 18 Jun 2007 08:21:59 +0200	[thread overview]
Message-ID: <200706180821.59582.arekm@maven.pl> (raw)
In-Reply-To: <20070618034322.GI18491@spearce.org>

On Monday 18 of June 2007, Shawn O. Pearce wrote:
> Arkadiusz Miskiewicz <arekm@maven.pl> wrote:
> > On Sunday 17 of June 2007, Junio C Hamano wrote:
> > > The latest maintenance release GIT 1.5.2.2 is available at the
> > > usual places:

[...]

> > Should git testsuite (make test) go without any problem? (I'm asking
> > because some projects have test suites where some tests are expected to
> > fail).
>
[...] 

>
> > * FAIL 16: corrupt a pack and see if verify catches
> >         cat test-1-${packname_1}.idx >test-3.idx &&
> >              cat test-2-${packname_2}.pack >test-3.pack &&
>
> Hmm.  That is t5300-pack-objects.sh.  Something is really fishy
> if that test failed.  We destroy a packfile and then look to see
> if the SHA-1 hash detects the change.  It always does.  So uh,
> what's up with your hardware that it doesn't fail?

There is no problems known with this hardware (kernel builds are frequently 
done on it and no problem occured so far). Test suite fails in the same place 
each time I'm running it.

> I just built 1.5.2.2 on one of my Gentoo Linux amd64 systems and I'm
> not seeing any failures from the test suite.  Not that I expected
> to find any; Linux amd64 is popular enough that a number of people
> run it.

Not all have the same enviroment. 

coreutils-6.9-2.x86_64
curl-7.16.2-1.x86_64
diffutils-2.8.7-4.x86_64
expat-2.0.0-3.x86_64
findutils-4.2.31-1.x86_64
gcc-4.2.0-6.x86_64
glibc-2.6-1.i686
glibc-2.6-1.x86_64
grep-2.5.1a-2.x86_64
openssl-0.9.8e-4.x86_64
perl-5.8.8-11.x86_64
python-2.5.1-2.x86_64
sed-4.1.5-2.x86_64
zlib-1.2.3-4.x86_64


If anyone is interested in debugging that problem then I can give ssh access 
to this machine.

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

  reply	other threads:[~2007-06-18  6:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17  1:57 [ANNOUNCE] GIT 1.5.2.2 Junio C Hamano
2007-06-17 10:30 ` Arkadiusz Miskiewicz
2007-06-18  3:43   ` Shawn O. Pearce
2007-06-18  6:21     ` Arkadiusz Miskiewicz [this message]
2007-06-18  6:29       ` Shawn O. Pearce
2007-06-18  6:35         ` Arkadiusz Miskiewicz
2007-06-18  3:27 ` Shawn O. Pearce
2007-06-20  8:34 ` Jakub Narebski
2007-07-12 20:57 ` [ANNOUNCE] GIT 1.5.2.4 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=200706180821.59582.arekm@maven.pl \
    --to=arekm@maven.pl \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=spearce@spearce.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).