From: Jens Lehmann <Jens.Lehmann@web.de>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v2] tests: print failed test numbers at the end of the test run
Date: Sun, 24 Jul 2011 21:21:15 +0200 [thread overview]
Message-ID: <4E2C70AB.2060306@web.de> (raw)
In-Reply-To: <20110724153950.GB7805@sigill.intra.peff.net>
Am 24.07.2011 17:39, schrieb Jeff King:
> On Sun, Jul 24, 2011 at 03:35:54PM +0200, Jens Lehmann wrote:
>
>> Am 24.07.2011 09:41, schrieb Junio C Hamano:
>>> Jens Lehmann <Jens.Lehmann@web.de> writes:
>>>
>>>> Maybe I'm missing something completely obvious, but I always have a hard
>>>> time finding out which test scripts did fail in a test run with -j30.
>>>
>>> I run "ls -d t/trash*" for that ;-)
>>
>> Yup. But that won't work when you use "-i" to continue to run all tests
>> even when some fail, as all trash directories get deleted in the end. Or
>> did I manage to overlook an option which stops that? ;-)
>
> I used to use:
>
> make -k -j30
> grep 'failed [^0]' test-results/*
Ah, now I understand how I managed to shoot myself in the foot when I tried
that: I used "-i" instead of "-k" for make, so the test-results directory
always was deleted after the tests ran.
> but these days I use the "prove" tool, which has much nicer output. You
> can get Makefile support for it with:
>
> GIT_PROVE_OPTS = -j30
> DEFAULT_TEST_TARGET = prove
>
> in your config.mak.
Thanks, the output really is nicer and it even runs a bit faster! :-)
next prev parent reply other threads:[~2011-07-24 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 19:16 [RFC PATCH] tests: print failed test numbers at the end of the test run Jens Lehmann
2011-07-24 7:41 ` Junio C Hamano
2011-07-24 13:35 ` [PATCH v2] " Jens Lehmann
2011-07-24 15:39 ` Jeff King
2011-07-24 19:21 ` Jens Lehmann [this message]
2011-07-25 14:31 ` Sverre Rabbelier
2011-07-26 4:25 ` [RFC PATCH] " Nguyen Thai Ngoc Duy
2011-07-26 5:42 ` Jeff King
2011-07-26 6:10 ` Jeff King
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=4E2C70AB.2060306@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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).