From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: John Keeping <john@keeping.me.uk>, Thomas Rast <tr@thomasrast.ch>
Subject: [PATCH 0/3] t0000 cleanups
Date: Sat, 28 Dec 2013 04:27:32 -0500 [thread overview]
Message-ID: <20131228092731.GA26337@sigill.intra.peff.net> (raw)
When I want to debug a failing test, I often end up doing:
cd t
./t4107-<tab> -v -i
cd tra<tab>
The test names are long, so tab-completing on the trash directory is
very helpful. Lately I've noticed that there are a bunch of crufty trash
directories in my t/ directory, which makes my tab-completion more
annoying.
It turns out they're leftovers from t0000 running, due to a bad
interaction with some other fixes from last April. The first patch fixes
that.
The second patch is a follow-on cleanup enabled by the first.
The third is an unrelated cleanup that I noticed when I ran t0000 47
times in a row. :)
[1/3]: t0000: set TEST_OUTPUT_DIRECTORY for sub-tests
[2/3]: t0000: simplify HARNESS_ACTIVE hack
[3/3]: t0000: drop "known breakage" test
t/t0000-basic.sh | 19 +++++++------------
t/test-lib.sh | 2 --
2 files changed, 7 insertions(+), 14 deletions(-)
-Peff
next reply other threads:[~2013-12-28 9:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 9:27 Jeff King [this message]
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
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=20131228092731.GA26337@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--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).