From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Patrick Steinhardt <ps@pks.im>,
git@vger.kernel.org,
Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: [PATCH] t0000: fix test if run with TEST_OUTPUT_DIRECTORY
Date: Tue, 20 Jul 2021 09:21:10 -0700 [thread overview]
Message-ID: <xmqq7dhlhs7d.fsf@gitster.g> (raw)
In-Reply-To: <YPZ3JmWKLrUldK4R@coredump.intra.peff.net> (Jeff King's message of "Tue, 20 Jul 2021 03:11:34 -0400")
Jeff King <peff@peff.net> writes:
> On Tue, Jul 20, 2021 at 08:32:26AM +0200, Patrick Steinhardt wrote:
>
>> Fix the issue by adding a new TEST_OUTPUT_DIRECTORY_OVERRIDE variable.
>> If set, then we'll always override the TEST_OUTPUT_DIRECTORY with its
>> value after sourcing GIT-BUILD-OPTIONS.
>
> Thanks, I like this approach much better than removing
> TEST_OUTPUT_DIRECTORY entirely (and I confirmed that it fixes the
> problem).
Yup, and it combines with your subtests-skip fix rather nicely to
solve both problems. Thanks for working well together.
> I do wish we had a more generic way of overriding stuff in
> GIT-BUILD-OPTIONS, rather than introducing manual _OVERRIDE variables
> for each. But there's not an easy solution here (see the earlier thread
> for some discussion), so this seems like a good immediate step to take.
>
> One small note on the commit message:
>
>> While this works as expected in the general case, it falls apart when
>> the developer has TEST_OUTPUT_DIRECTORY explicitly defined either via
>> the environment or via config.mak.
>
> The mention of the environment confused me for a moment, since:
>
> TEST_OUTPUT_DIRECTORY=/tmp/foo ./t0000-basic.sh
>
> is already OK. But you probably meant that:
>
> TEST_OUTPUT_DIRECTORY=/tmp/foo make test
>
> would fail, since "make" would pick up the variable and then write it
> into GIT-BUILD-OPTIONS (just as it would if you put it in config.mak, or
> on the command-line of make).
>
> I don't think it's sufficiently confusing to rewrite the commit message,
> but just something I noted while reading it.
I'll just insert "and runs 'make test'" after "via config.mak" while
queuing.
Again, thanks, both.
next prev parent reply other threads:[~2021-07-20 16:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 1:07 What's cooking in git.git (Jul 2021, #03; Tue, 13) Junio C Hamano
2021-07-14 2:16 ` Eric Sunshine
2021-07-14 16:30 ` Junio C Hamano
2021-07-14 22:39 ` Eric Sunshine
2021-07-14 22:44 ` Junio C Hamano
2021-07-14 8:42 ` Han-Wen Nienhuys
2021-07-14 11:53 ` Ævar Arnfjörð Bjarmason
2021-07-14 11:54 ` Ævar Arnfjörð Bjarmason
2021-07-14 17:28 ` Junio C Hamano
2021-07-14 13:11 ` Derrick Stolee
2021-07-14 14:32 ` Ævar Arnfjörð Bjarmason
2021-07-15 16:25 ` [PATCH] CodingGuidelines: recommend gender-neutral description Junio C Hamano
2021-07-15 16:35 ` Eric Sunshine
2021-07-15 16:47 ` Taylor Blau
2021-07-15 18:02 ` Junio C Hamano
2021-07-16 21:25 ` Felipe Contreras
2021-07-15 17:27 ` Derrick Stolee
2021-07-16 15:11 ` Johannes Schindelin
2021-07-16 21:22 ` Felipe Contreras
2021-07-16 18:41 ` [PATCH v2] " Junio C Hamano
2021-07-16 19:05 ` Derrick Stolee
2021-07-16 19:11 ` Ævar Arnfjörð Bjarmason
2021-07-16 19:50 ` Junio C Hamano
2021-07-16 21:14 ` Felipe Contreras
2021-08-12 8:35 ` [PATCH] " Bagas Sanjaya
2021-07-14 20:11 ` What's cooking in git.git (Jul 2021, #03; Tue, 13) Taylor Blau
2021-07-19 7:35 ` Patrick Steinhardt
2021-07-19 7:53 ` Felipe Contreras
2021-07-19 8:35 ` Jeff King
2021-07-19 10:42 ` Felipe Contreras
2021-07-19 10:56 ` Patrick Steinhardt
2021-07-19 11:25 ` Felipe Contreras
2021-07-19 8:33 ` Jeff King
2021-07-19 10:41 ` Patrick Steinhardt
2021-07-19 10:52 ` Jeff King
2021-07-19 18:40 ` Junio C Hamano
2021-07-19 19:57 ` Felipe Contreras
2021-07-20 6:31 ` Patrick Steinhardt
2021-07-20 7:21 ` Felipe Contreras
2021-07-20 6:32 ` [PATCH] t0000: fix test if run with TEST_OUTPUT_DIRECTORY Patrick Steinhardt
2021-07-20 7:11 ` Jeff King
2021-07-20 16:21 ` Junio C Hamano [this message]
2021-07-20 7:24 ` 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=xmqq7dhlhs7d.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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).