From: Jonathan Nieder <jrnieder@gmail.com>
To: "Gary V. Vaughan" <git@mlists.thewrittenword.com>
Cc: git@vger.kernel.org
Subject: Re: Massive testsuite failure on !(Linux || Solaris 8+)
Date: Mon, 26 Apr 2010 02:44:11 -0500 [thread overview]
Message-ID: <20100426074411.GA31428@progeny.tock> (raw)
In-Reply-To: <20100316100917.GA27121@thor.il.thewrittenword.com>
Hi Gary,
Gary V. Vaughan wrote:
> I have full logs on all hosts, up until t9300 test 120, which hangs (I
> left it overnight to be sure since some of these machines are quite
> old and slow) the testsuite until SIGINT. The logs are, obviously,
> huge so I won't post them here,
What tends be most useful is output from
GIT_TEST_OPTS='-v -i' gmake test
This way you can see the actual output from the failing commands, and
you only have to worry about the first test that fails (no doubt the
later ones are similar). Certainly if any tests from t0000-basic.sh
are failing, it is useless to worry about problems in later tests.
Options for use when invoking tests are documented in t/README.
Also, if you would like to investigate, you might find it useful to
use
sh -x relevant-test.sh
Based on the list of failing tests, though, it seems that your
test_cmp is not working correctly. You should make sure that the
GIT_TEST_CMP environment variable is set to point to some command that
will exit with status 0 if the two files are identical and with nonzero
status if they differ. I imagine patches to the Makefile and
t/Makefile to set this up appropriately for your platforms (without
ruining the nice diff output for overone else) would be welcome.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2010-04-26 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-25 8:40 Massive testsuite failure on !(Linux || Solaris 8+) Gary V. Vaughan
2010-04-26 7:44 ` Jonathan Nieder [this message]
2010-04-26 17:03 ` Gary V. Vaughan
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=20100426074411.GA31428@progeny.tock \
--to=jrnieder@gmail.com \
--cc=git@mlists.thewrittenword.com \
--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).