Re: [ANNOUNCE] GIT 1.5.2.2
- From
Shawn O. Pearce <spearce@spearce.org>
- Date
- Jun 18, 2007, 03:43 UTC
- Message-ID
- <20070618034322.GI18491@spearce.org>
- In-Reply-To
- <200706171230.37659.arekm@maven.pl>
Arkadiusz Miskiewicz <arekm@maven.pl> wrote:
Show 13 quoted lines
> 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:
> >
> > http://www.kernel.org/pub/software/scm/git/
> >
> > git-1.5.2.2.tar.{gz,bz2} (tarball)
> > git-htmldocs-1.5.2.2.tar.{gz,bz2} (preformatted docs)
> > git-manpages-1.5.2.2.tar.{gz,bz2} (preformatted docs)
> > RPMS/$arch/git-*-1.5.2.2-1.$arch.rpm (RPM)
>
> 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).No, our test suite should always pass. Junio does not ship a release of Git where the test suite fails on his standard systems. We have a lot of users running the current `master` and `next` branches on a lot of different platforms, so usually platform specific breakages are caught relatively early, before a release gets made.
We do have tests we expect to fail, but then the test suite has an inversion in it. That is the test only passes if the underlying operation failed. ;-)
> I have 4 failures on amd64/linux and this git release:
...
> * 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?
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.
-- Shawn.