git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
	Git Mailing List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC PATCH] tests: print failed test numbers at the end of the test run
Date: Mon, 25 Jul 2011 23:42:36 -0600	[thread overview]
Message-ID: <20110726054236.GC25046@sigill.intra.peff.net> (raw)
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:

> 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

  reply	other threads:[~2011-07-26  5:42 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
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 [this message]
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=20110726054236.GC25046@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    /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).