From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
git@vger.kernel.org
Subject: Re: [RFC PATCH] Makefile: new prove target for running the tests with TAP
Date: Wed, 27 Oct 2010 13:00:15 +0200 [thread overview]
Message-ID: <AANLkTimH=fbRAdz-F-V-9WTKzAyVvpzRHC06e+94a2wJ@mail.gmail.com> (raw)
In-Reply-To: <20101027045709.GA11250@idm.gtisc.gatech.edu>
On Wed, Oct 27, 2010 at 06:57, Jeff King <peff@peff.net> wrote:
> On Tue, Oct 26, 2010 at 05:18:22PM -0700, Junio C Hamano wrote:
>
>> > like -j16, but it's a pain to construct the command line (especially as
>> > I use --root in GIT_TEST_OPTS to get a significant speedup).
>> [..]
>> I kind of like this. Perhaps with something like this squashed in?
>
> Yeah, looks good to me. I guess you can steal the commit message and
> authorship from Michael's original.
>
> Ævar mentioned something about t/harness, which I honestly have no idea
> about (I don't have the right perl modules installed to run it). But
> maybe that could be an alternate DEFAULT_TEST_TARGET. I dunno.
The non-standard module there is only needed for the smoke testing.
If we used t/harness for running "make test" that code could be
modified to run anywhere prove itself does.
Anyway, if there's a patch now to invoke prove(1) let's use that. We
can change it to t/harness later if that makes sense.
next prev parent reply other threads:[~2010-10-27 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 8:53 [RFC PATCH] Makefile: new prove target for running the tests with TAP Michael J Gruber
2010-10-14 9:05 ` Ævar Arnfjörð Bjarmason
2010-10-14 9:21 ` Michael J Gruber
2010-10-14 9:33 ` Ævar Arnfjörð Bjarmason
2010-10-14 16:27 ` Jonathan Nieder
2010-10-14 17:23 ` Jeff King
2010-10-27 0:18 ` Junio C Hamano
2010-10-27 4:57 ` Jeff King
2010-10-27 11:00 ` Ævar Arnfjörð Bjarmason [this message]
2010-10-29 13:19 ` Michael J Gruber
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimH=fbRAdz-F-V-9WTKzAyVvpzRHC06e+94a2wJ@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=git@drmicha.warpmail.net \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).