git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] tests: print failed test numbers at the end of the test run

From
Jens Lehmann <jens.lehmann@web.de>
Date
Jul 24, 2011, 19:21 UTC
Message-ID
<4E2C70AB.2060306@web.de>
In-Reply-To
<20110724153950.GB7805@sigill.intra.peff.net>
Am 24.07.2011 17:39, schrieb Jeff King:
Show 18 quoted lines
> 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.

Show 7 quoted lines
> 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! :-)
Previous: Jeff KingNext: Sverre Rabbelier
Message 5 of 9 in “tests: print failed test numbers at the end of the test run”
  1. tests: print failed test numbers at the end of the test runJens Lehmann, Jul 23, 2011
  2. Junio C HamanoJul 24, 2011
  3. tests: print failed test numbers at the end of the test runJens Lehmann, Jul 24, 2011
  4. Jeff KingJul 24, 2011
  5. Jens LehmannJul 24, 2011
  6. Sverre RabbelierJul 25, 2011
  7. Nguyen Thai Ngoc DuyJul 26, 2011
  8. Jeff KingJul 26, 2011
  9. Jeff KingJul 26, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.