From: Michael J Gruber <michaeljgruber+gmane@fastmail.fm>
To: git@vger.kernel.org
Subject: Test breakage [Re: [ANNOUNCE] GIT 1.5.6.2]
Date: Mon, 07 Jul 2008 14:44:49 +0200 [thread overview]
Message-ID: <g4t342$9m8$1@ger.gmane.org> (raw)
In-Reply-To: <7vy74fo9t4.fsf@gitster.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 06.07.2008 07:34:
> The latest maintenance release GIT 1.5.6.2 are available at the usual
> places:
...
On Kubuntu 7.10 (not my choice, this is at work...), "make test" gives:
*** t9600-cvsimport.sh ***
* ok 1: setup cvsroot
* ok 2: setup a cvs module
* ok 3: import a trivial module
* ok 4: pack refs
* ok 5: update cvs module
* FAIL 6: update git module
cd module-git &&
git cvsimport -a -z 0 module &&
git merge origin &&
cd .. &&
test_cmp module-cvs/o_fortuna module-git/o_fortuna
* ok 7: update cvs module
* ok 8: cvsimport.module config works
* ok 9: import from a CVS working tree
* failed 1 among 9 test(s)
On the second (and subsequent) run, "make test" succeeds. I tried again
with a fresh copy from the tarball, same effect: failure on 1, success
on 2 and following.
This is with LANG=de_DE.UTF-8, whereas with LANG=C the tests succeed the
first time already. Are tests supposed to be done in C locale only? Do
they reuse data from a previous test run? I didn't notice this with 1.5.6.1.
Michael
next prev parent reply other threads:[~2008-07-07 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 5:34 [ANNOUNCE] GIT 1.5.6.2 Junio C Hamano
2008-07-06 8:09 ` Jakub Narebski
2008-07-06 9:30 ` Junio C Hamano
2008-07-06 12:44 ` Jan Engelhardt
2008-07-06 14:54 ` Mikael Magnusson
2008-07-07 12:44 ` Michael J Gruber [this message]
2008-07-08 5:16 ` Test breakage [Re: [ANNOUNCE] GIT 1.5.6.2] Jeff King
2008-07-08 9:47 ` Michael J Gruber
2008-07-14 3:13 ` [ANNOUNCE] GIT 1.5.6.3 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='g4t342$9m8$1@ger.gmane.org' \
--to=michaeljgruber+gmane@fastmail.fm \
--cc=git@vger.kernel.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).