git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
	"Antoine Pelisse" <apelisse@gmail.com>,
	"Felipe Contreras" <felipe.contreras@gmail.com>,
	git <git@vger.kernel.org>
Subject: Re: [PATCH 1/3] remote-helpers: fix the run of all tests
Date: Wed, 03 Apr 2013 07:57:04 -0700	[thread overview]
Message-ID: <7v8v4z7jcv.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130402173652.GC24698@sigill.intra.peff.net> (Jeff King's message of "Tue, 2 Apr 2013 13:36:52 -0400")

Jeff King <peff@peff.net> writes:

> On Tue, Apr 02, 2013 at 06:53:28PM +0200, Torsten Bögershausen wrote:
>
>> > I think the check for duplicate-numbers is the only one that does not
>> > make sense. 
>> []
>> Not sure about that, I send a suggestion of a patch in a minute.
>> Highlights:
>> 1) - rename the contrib test cases and assigns real TC numbers
>> 2) - Forward the numbers into the main "test Makefile"
>
> I'm not sure if this is a good idea or not.

If that's a polite way to say that this is not a good idea, I'd
agree for all the reasons you mentioned.

> It puts the
> contrib/remote-helpers into the same "number namespace" as the rest of
> the test scripts, and enforces uniqueness with test-lint-duplicates,
> when "make test" is run from contrib/remote-helpers. But people working
> on the main test scripts would not get any such check, and would happily
> break contrib/remote-helpers by adding duplicate test numbers.
>
> It makes sense to me to either:
>
>   1. Have the contrib/remote-helpers test live in their own test
>      namespace completely, with their own numbers and test-results, and
>      pull in relevant bits from the main test harness. We do this
>      already with contrib/subtree.  I suggested this when the tests
>      first appeared, but there was some argument, and I don't remember
>      the details.

This makes more sense than the alternative, given that contrib/
material is "optional" from the main tree's point of view, at least
to me.

Thanks.

>   2. Just integrate contrib test scripts into the main repository, but
>      leave them off by default. For example, add:
>
>        if test -z "$GIT_TEST_REMOTE_HELPERS"; then
>               skip_all="Remote helper tests disabled (define GIT_TEST_REMOTE_HELPERS)"
>               test_done
>        fi
>
>      to the top of the scripts, and then set GIT_TEST_REMOTE_HELPERS
>      in contrib/remote-helpers/Makefile before chaining to the test
>      Makefile.

  parent reply	other threads:[~2013-04-03 14:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01 21:14 [PATCH 0/3] remote-helpers: trivial test fixes Felipe Contreras
2013-04-01 21:14 ` [PATCH 1/3] remote-helpers: fix the run of all tests Felipe Contreras
2013-04-01 21:46   ` Antoine Pelisse
2013-04-01 23:40     ` Jeff King
2013-04-02 16:53       ` Torsten Bögershausen
2013-04-02 17:36         ` Jeff King
2013-04-03  5:53           ` Torsten Bögershausen
2013-04-03 14:57           ` Junio C Hamano [this message]
2013-04-04 15:36       ` Felipe Contreras
2013-04-01 21:14 ` [PATCH 2/3] remote-bzr: remove stale check code for tests Felipe Contreras
2013-04-01 22:46   ` Junio C Hamano
2013-04-01 21:14 ` [PATCH 3/3] remote-hg: fix hg-git test-case Felipe Contreras
2013-04-01 21:48 ` [PATCH 0/3] remote-helpers: trivial test fixes Antoine Pelisse
2013-04-01 21:56   ` Felipe Contreras
2013-04-01 22:46     ` Felipe Contreras

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=7v8v4z7jcv.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=apelisse@gmail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=tboegi@web.de \
    /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).