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

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

From
Jeff King <peff@peff.net>
Date
Jul 26, 2011, 05:42 UTC
Message-ID
<20110726054236.GC25046@sigill.intra.peff.net>
In-Reply-To
<CACsJy8CuqHSoG4PVMiT=5EUv2hn=42y5B+6Rhny2VkXW32WR8Q@mail.gmail.com>
On Tue, Jul 26, 2011 at 11:25:21AM +0700, Nguyen Thai Ngoc Duy wrote:
Show 10 quoted lines
> On Sun, Jul 24, 2011 at 2:16 AM, Jens Lehmann <Jens.Lehmann@web.de> wrote:
> > On modern multi-core processors "make test" is often run in multiple jobs.
> > If one of them fails the test run does stop, but the concurrently running
> > tests finish their run.
> 
> Somewhat related (or not). I change something. I know it breaks things
> and want to know _all_ tests it breaks, but "make test" would stop
> early. Is there anyway to make it keep going through all tests even if
> some fails? "make -j<big number>" improves the situation but does not
> really solve it.

Try "make -k", which will keep running rules that don't have failed dependencies (in this case, all of the tests are independent, so it will run all of them).

Or use "prove", which can do fancy things like putting the last-failed (so you can see the likely failures immediately and start to probe them while the rest of the suite runs).

-Peff
Previous: Nguyen Thai Ngoc DuyNext: Jeff King
Message 8 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.