git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>, Felipe Contreras <felipe.contreras@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2021, #03; Tue, 13)
Date: Mon, 19 Jul 2021 05:42:59 -0500	[thread overview]
Message-ID: <60f5573312036_13ce8720841@natae.notmuch> (raw)
In-Reply-To: <YPU5NyoDrQquWOYo@coredump.intra.peff.net>

Jeff King wrote:
> On Mon, Jul 19, 2021 at 02:53:30AM -0500, Felipe Contreras wrote:
> 
> > Patrick Steinhardt wrote:
> > > On Tue, Jul 13, 2021 at 06:07:12PM -0700, Junio C Hamano wrote:
> > > [snip]
> > > > * ps/perf-with-separate-output-directory (2021-07-02) 1 commit
> > > >  - perf: fix when running with TEST_OUTPUT_DIRECTORY
> > > > 
> > > >  Test update.
> > > > 
> > > >  What's the status of this one?
> > > 
> > > From my point of view this is ready, but it's still missing reviews so
> > > far. The lack of interest seems to indicate that nobody has hit the
> > > issue so far, and I wonder why that is. Am I the only one who sets
> > > TEST_OUTPUT_DIRECTORY to a tmpfs directory in his config.mak to speed up
> > > tests?
> > 
> > No, I do the same, and this other fix for TEST_OUTPUT_DIRECTORY is being
> > ignored even harder:
> > 
> > https://lore.kernel.org/git/20210707030709.3134859-1-felipe.contreras@gmail.com/
> 
> Note that the linked patch will break Patrick's, because we would no
> longer set TEST_OUTPUT_DIRECTORY in GIT-BUILD-OPTIONS.

Is Patrick's patch specific to GIT-BUILD-OPTIONS? Or can
TEST_OUTPUT_DIRECTORY be taken from the environment?

Either way I think the priority should be to make the standard tests
work with TEST_OUTPUT_DIRECTORY.

-- 
Felipe Contreras

  reply	other threads:[~2021-07-19 10:43 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 [this message]
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
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

  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=60f5573312036_13ce8720841@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.
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).