From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, John Keeping <john@keeping.me.uk>,
Thomas Rast <tr@thomasrast.ch>
Subject: Re: [PATCH 1/3] t0000: set TEST_OUTPUT_DIRECTORY for sub-tests
Date: Sat, 28 Dec 2013 14:20:03 -0800 [thread overview]
Message-ID: <20131228222003.GD5544@google.com> (raw)
In-Reply-To: <20131228221313.GB5544@google.com>
Jonathan Nieder wrote:
> - git used to only use TEST_OUTPUT_DIRECTORY to decide where test
> results go. You'd have to use --root to set a custom location for
> trash directories.
>
> - in that old setup, t0000 leaves around extra trash directories with
> --root, since the sub-tests inherit the parent test's $root and put
> trash directories there.
Nope, since sub-tests are run with fork + exec, which loses $root...
> - after 38b074d, that old problem still exists and furthermore
> t0000 leaves around extra trash directories even when --root is not
> in use, since the sub-tests inherit the value of
> TEST_OUTPUT_DIRECTORY from the parent test.
... meaning the TEST_OUTPUT_DIRECTORY problem is the only problem....
> - this patch fixes the TEST_OUTPUT_DIRECTORY problem (but not the $root
> problem) by setting TEST_OUTPUT_DIRECTORY explicitly
>
> Does that sound right? If so, should sub-tests unset $root, too?
... and there's no need to 'unset root'.
So the patch itself looks right. I think describing the symptoms up
front would probably be enough to make the commit message less
confusing to read.
Jonathan
next prev parent reply other threads:[~2013-12-28 22:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 9:27 [PATCH 0/3] t0000 cleanups Jeff King
2013-12-28 9:29 ` [PATCH 1/3] t0000: set TEST_OUTPUT_DIRECTORY for sub-tests Jeff King
2013-12-28 22:13 ` Jonathan Nieder
2013-12-28 22:20 ` Jonathan Nieder [this message]
2013-12-29 7:17 ` Jeff King
2013-12-28 9:31 ` [PATCH 2/3] t0000: simplify HARNESS_ACTIVE hack Jeff King
2013-12-28 22:14 ` Jonathan Nieder
2013-12-28 9:33 ` [PATCH 3/3] t0000: drop "known breakage" test Jeff King
2013-12-28 20:51 ` Jonathan Nieder
2013-12-29 7:22 ` Jeff King
2013-12-28 22:21 ` [PATCH 0/3] t0000 cleanups Jonathan Nieder
2013-12-30 18:30 ` Junio C Hamano
2013-12-30 18:51 ` Jonathan Nieder
2013-12-30 19:24 ` Junio C Hamano
2013-12-31 10:33 ` Jeff King
2014-01-02 22:28 ` Jonathan Nieder
2014-01-02 22:41 ` Junio C Hamano
2014-01-03 1:04 ` 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=20131228222003.GD5544@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=peff@peff.net \
--cc=tr@thomasrast.ch \
/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).