From: Jonathan Nieder <jrnieder@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2 2/5] t/t4004-diff-rename-symlink.sh: use three-arg <prereq>
Date: Wed, 28 Jul 2010 20:09:03 -0500 [thread overview]
Message-ID: <20100729010903.GF29156@dert.cs.uchicago.edu> (raw)
In-Reply-To: <1280313299-721-3-git-send-email-avarab@gmail.com>
Ævar Arnfjörð Bjarmason wrote:
> Change the tests that skipped due to unavailable SYMLINKS support to
> use the three-arg prereq form of test_expect_success.
>
> This is like the "tests: implicitly skip SYMLINKS tests using
> <prereq>" change, but I needed to create an additional test for some
> setup code. It's in a separate change as suggested by Jonathan Nieder
> for ease of reviewing.
Hmm, I still don’t understand this. Do you mean that there is
some setup that needs to be run before these commands, and so
the patch fails if that change is not included?
Or is it a matter of "while at it, fix this other problem
I noticed" (which would be fine, but it is clearer to
present it as such if so)?
> diff --git a/t/t4004-diff-rename-symlink.sh b/t/t4004-diff-rename-symlink.sh
> index 1a09e8d..92a65f4 100755
> --- a/t/t4004-diff-rename-symlink.sh
> +++ b/t/t4004-diff-rename-symlink.sh
> @@ -40,8 +34,9 @@ test_expect_success \
> # rezrov and nitfol are rename/copy of frotz and bozbar should be
> # a new creation.
>
> -GIT_DIFF_OPTS=--unified=0 git diff-index -M -p $tree >current
> -cat >expected <<\EOF
> +test_expect_success SYMLINKS 'setup diff output' "
> + GIT_DIFF_OPTS=--unified=0 git diff-index -M -p $tree >current &&
> + cat >expected <<\EOF
> diff --git a/bozbar b/bozbar
> new file mode 120000
> --- /dev/null
> @@ -65,8 +60,9 @@ deleted file mode 100644
> -xyzzy
> \ No newline at end of file
> EOF
> +"
Tip for the future: if you use 'straight quotes', then readers
can avoid carefully scanning through for $ and similar oddities
(and the test script presented with the "expecting success:"
prompt will use the friendlier $tree instead of 76c98ds89).
The patch looks good; my only remaining concern is the log
message as mentioned above.
Thanks,
Jonathan
next prev parent reply other threads:[~2010-07-29 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 10:34 [PATCH v2 0/5] Skip tests using 3-arg test_* Ævar Arnfjörð Bjarmason
2010-07-28 10:34 ` [PATCH v2 1/5] tests: implicitly skip SYMLINKS tests using <prereq> Ævar Arnfjörð Bjarmason
2010-07-29 1:00 ` Jonathan Nieder
2010-07-28 10:34 ` [PATCH v2 2/5] t/t4004-diff-rename-symlink.sh: use three-arg <prereq> Ævar Arnfjörð Bjarmason
2010-07-29 1:09 ` Jonathan Nieder [this message]
2010-07-29 1:56 ` Ævar Arnfjörð Bjarmason
2010-07-28 10:34 ` [PATCH v2 3/5] t/t5800-remote-helpers.sh: Skip with prereq on python <2.4 Ævar Arnfjörð Bjarmason
2010-07-29 1:16 ` Jonathan Nieder
2010-07-29 2:03 ` Ævar Arnfjörð Bjarmason
2010-07-28 10:34 ` [PATCH v2 4/5] t/t7800-difftool.sh: Skip with prereq on no PERL Ævar Arnfjörð Bjarmason
2010-07-28 10:34 ` [PATCH v2 5/5] t/README: Update "Skipping tests" to align with best practices Ævar Arnfjörð Bjarmason
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=20100729010903.GF29156@dert.cs.uchicago.edu \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).