From: Jonathan Nieder <jrnieder@gmail.com>
To: Matthew DeVore <matvore@google.com>
Cc: git@vger.kernel.org, peff@peff.net, jonathantanmy@google.com,
gitster@pobox.com, bmwill@google.com
Subject: Re: [PATCH v1 1/2] t/*: fix pipe placement and remove \'s
Date: Mon, 17 Sep 2018 09:31:37 -0700 [thread overview]
Message-ID: <20180917163137.GB89942@aiede.svl.corp.google.com> (raw)
In-Reply-To: <a4c833da81d83ea0e605c936d90ea9c7f5667d93.1536969438.git.matvore@google.com>
Matthew DeVore wrote:
> Subject: t/*: fix pipe placement and remove \'s
>
> Where ever there was code in the tests like this:
>
> foo \
> | bar
Language nits:
- s/Where ever/Wherever/
- Git's commit messages use the present tense to describe the existing
previous state of the codebase, as though reporting a bug.
Maybe something like
tests: standardize pipe placement
Instead of using a line-continuation and pipe on the second
line, take advantage of the shell's implicit line continuation
after a pipe character. So for example, instead of
some long line \
| next line
use
some long line |
next line
At this point, it would be useful to say something about rationale ---
for example,
This better matches the coding style documented in
Documentation/CodingGuidelines and used in shell scripts
elsewhere in Git.
Except: is this documented in Documentation/CodingGuidelines? Or,
better, is there a linter that we can run in the test-lint target of
t/Makefile to ensure we keep sticking to this style?
[...]
> --- a/t/lib-gpg.sh
> +++ b/t/lib-gpg.sh
> @@ -57,8 +57,8 @@ then
> echo | gpgsm --homedir "${GNUPGHOME}" 2>/dev/null \
> --passphrase-fd 0 --pinentry-mode loopback \
> --import "$TEST_DIRECTORY"/lib-gpg/gpgsm_cert.p12 &&
> - gpgsm --homedir "${GNUPGHOME}" 2>/dev/null -K \
> - | grep fingerprint: | cut -d" " -f4 | tr -d '\n' > \
> + gpgsm --homedir "${GNUPGHOME}" 2>/dev/null -K |
> + grep fingerprint: | cut -d" " -f4 | tr -d '\n' > \
> ${GNUPGHOME}/trustlist.txt &&
I think this would be more readable with one item from the pipeline
per line:
gpgsm --homedir ... |
grep ... |
cut ... |
tr ... >... &&
[...]
> --- a/t/t1006-cat-file.sh
> +++ b/t/t1006-cat-file.sh
> @@ -218,8 +218,8 @@ test_expect_success "--batch-check for a non-existent hash" '
> test "0000000000000000000000000000000000000042 missing
> 0000000000000000000000000000000000000084 missing" = \
> "$( ( echo 0000000000000000000000000000000000000042;
> - echo_without_newline 0000000000000000000000000000000000000084; ) \
> - | git cat-file --batch-check)"
> + echo_without_newline 0000000000000000000000000000000000000084; ) |
> + git cat-file --batch-check)"
This test is problematic in a lot of ways. Most importantly, it ignores
the exist status from git cat-file.
So it should say something like:
cat >expect <<-\EOF &&
foobar42 missing
foobar84 missing
EOF
printf "foobar42\nfoobar84" |
git cat-file --batch-check >actual &&
test_cmp expect actual
If we want to restrict to the pipeline style fixes, we could do
test "..." = "$(
{ # Couldn't resist changing the ( to {!
echo ... && # Couldn't resist changing the ; to &&!
echo_without_newline ...
} |
git cat-file --batch-check
)"
but unless there's a linter that we're helping support, it's probably
better to skip this file and use a dedicated patch to modernize its
style more generally.
[...]
> --- a/t/t1300-config.sh
> +++ b/t/t1300-config.sh
> @@ -1770,8 +1770,9 @@ test_expect_success '--show-origin stdin with file include' '
> cat >expect <<-EOF &&
> file:$INCLUDE_DIR/stdin.include include
> EOF
> - echo "[include]path=\"$INCLUDE_DIR\"/stdin.include" \
> - | git config --show-origin --includes --file - user.stdin >output &&
> + echo "[include]path=\"$INCLUDE_DIR\"/stdin.include" |
> + git config --show-origin --includes --file - user.stdin >output &&
Okay.
[...]
> --- a/t/t5317-pack-objects-filter-objects.sh
> +++ b/t/t5317-pack-objects-filter-objects.sh
> @@ -20,17 +20,20 @@ test_expect_success 'setup r1' '
> '
>
> test_expect_success 'verify blob count in normal packfile' '
> - git -C r1 ls-files -s file.1 file.2 file.3 file.4 file.5 \
> - | awk -f print_2.awk \
> - | sort >expected &&
> + git -C r1 ls-files -s file.1 file.2 file.3 file.4 file.5 |
> + awk -f print_2.awk |
> + sort >expected &&
This loses the exit status from git, so we should make it write to a
temporary file instead (as a separate patch).
[...]
> - git -C r1 verify-pack -v ../all.pack \
> - | grep blob \
> - | awk -f print_1.awk \
> - | sort >observed &&
> +
> + git -C r1 verify-pack -v ../all.pack |
Likewise (and likewise for the rest in this file).
[...]
> --- a/t/t5500-fetch-pack.sh
> +++ b/t/t5500-fetch-pack.sh
> @@ -50,8 +50,9 @@ pull_to_client () {
> case "$heads" in *B*)
> git update-ref refs/heads/B "$BTIP";;
> esac &&
> - git symbolic-ref HEAD refs/heads/$(echo $heads \
> - | sed -e "s/^\(.\).*$/\1/") &&
> +
> + git symbolic-ref HEAD refs/heads/$(echo $heads |
> + sed -e "s/^\(.\).*$/\1/") &&
It would be better to use a temporary variable. If we're just
changing line wrapping, then this would be
git symbolic-ref HAD refs/heads/$(
echo $heads |
sed ...
) &&
[...]
> --- a/t/t5616-partial-clone.sh
> +++ b/t/t5616-partial-clone.sh
> @@ -34,10 +34,12 @@ test_expect_success 'setup bare clone for server' '
> # confirm partial clone was registered in the local config.
> test_expect_success 'do partial clone 1' '
> git clone --no-checkout --filter=blob:none "file://$(pwd)/srv.bare" pc1 &&
> - git -C pc1 rev-list HEAD --quiet --objects --missing=print \
> - | awk -f print_1.awk \
> - | sed "s/?//" \
> - | sort >observed.oids &&
> +
> + git -C pc1 rev-list HEAD --quiet --objects --missing=print |
Also needs to write to a temporary to avoid losing the exist status
(and likewise for the rest of this file).
[...]
> --- a/t/t6112-rev-list-filters-objects.sh
> +++ b/t/t6112-rev-list-filters-objects.sh
> @@ -20,24 +20,28 @@ test_expect_success 'setup r1' '
> '
>
> test_expect_success 'verify blob:none omits all 5 blobs' '
> - git -C r1 ls-files -s file.1 file.2 file.3 file.4 file.5 \
> - | awk -f print_2.awk \
> - | sort >expected &&
> - git -C r1 rev-list HEAD --quiet --objects --filter-print-omitted --filter=blob:none \
> - | awk -f print_1.awk \
> - | sed "s/~//" \
> - | sort >observed &&
> + git -C r1 ls-files -s file.1 file.2 file.3 file.4 file.5 |
> + awk -f print_2.awk |
> + sort >expected &&
Likewise.
[...]
> --- a/t/t9101-git-svn-props.sh
> +++ b/t/t9101-git-svn-props.sh
> @@ -193,8 +193,8 @@ test_expect_success 'test propget' "
> git svn propget svn:ignore . | cmp - prop.expect &&
> cd deeply &&
> git svn propget svn:ignore . | cmp - ../prop.expect &&
> - git svn propget svn:entry:committed-rev nested/directory/.keep \
> - | cmp - ../prop2.expect &&
> + git svn propget svn:entry:committed-rev nested/directory/.keep |
> + cmp - ../prop2.expect &&
Likewise.
Thanks and hope that helps,
Jonathan
next prev parent reply other threads:[~2018-09-17 16:31 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 0:02 [PATCH v1 0/2] Cleanup tests for test_cmp argument ordering and "|" placement Matthew DeVore
2018-09-15 0:02 ` [PATCH v1 1/2] t/*: fix pipe placement and remove \'s Matthew DeVore
2018-09-17 16:31 ` Jonathan Nieder [this message]
2018-09-17 21:47 ` Matthew DeVore
2018-09-15 0:02 ` [PATCH v1 2/2] t/*: fix ordering of expected/observed arguments Matthew DeVore
2018-09-17 12:56 ` Matthew DeVore
2018-09-15 15:55 ` [PATCH v1 0/2] Cleanup tests for test_cmp argument ordering and "|" placement Junio C Hamano
2018-09-17 22:24 ` [PATCH v2 0/6] Clean up tests for test_cmp arg ordering and pipe placement Matthew DeVore
2018-09-17 22:24 ` [PATCH v2 4/6] tests: Add linter check for pipe placement style Matthew DeVore
2018-09-18 0:34 ` Eric Sunshine
2018-09-19 17:39 ` Matthew DeVore
[not found] ` <cover.1537223021.git.matvore@google.com>
2018-09-17 22:24 ` [PATCH v2 1/6] CodingGuidelines: add shell piping guidelines Matthew DeVore
2018-09-18 0:16 ` Eric Sunshine
2018-09-19 2:11 ` Matthew DeVore
2018-09-19 12:36 ` Eric Sunshine
2018-09-19 14:24 ` Junio C Hamano
2018-09-19 20:06 ` Matthew DeVore
2018-09-17 22:24 ` [PATCH v2 2/6] tests: standardize pipe placement Matthew DeVore
2018-09-17 22:24 ` [PATCH v2 3/6] t/*: fix ordering of expected/observed arguments Matthew DeVore
2018-09-17 22:24 ` [PATCH v2 4/6] tests: add linter check for pipe placement style Matthew DeVore
2018-09-17 22:24 ` [PATCH v2 5/6] tests: split up pipes Matthew DeVore
2018-09-18 1:30 ` Eric Sunshine
2018-09-19 2:33 ` Matthew DeVore
2018-09-17 22:24 ` [PATCH v2 6/6] t9109-git-svn-props.sh: split up several pipes Matthew DeVore
2018-09-18 1:56 ` Eric Sunshine
2018-09-19 2:56 ` Matthew DeVore
2018-09-19 12:50 ` Eric Sunshine
2018-09-19 18:43 ` Matthew DeVore
2018-09-21 1:43 ` [PATCH v3 0/5] Clean up tests for test_cmp arg ordering and pipe placement Matthew DeVore
2018-09-21 1:43 ` [PATCH v3 1/5] CodingGuidelines: add shell piping guidelines Matthew DeVore
2018-09-21 2:06 ` Eric Sunshine
2018-09-21 21:03 ` Matthew DeVore
2018-09-24 21:03 ` SZEDER Gábor
2018-09-25 21:58 ` Matthew DeVore
2018-09-27 21:18 ` SZEDER Gábor
2018-10-01 23:07 ` Matthew DeVore
2018-09-21 1:43 ` [PATCH v3 2/5] tests: standardize pipe placement Matthew DeVore
2018-09-21 1:43 ` [PATCH v3 3/5] t/*: fix ordering of expected/observed arguments Matthew DeVore
2018-09-21 1:43 ` [PATCH v3 4/5] tests: don't swallow Git errors upstream of pipes Matthew DeVore
2018-09-21 1:43 ` [PATCH v3 5/5] t9109: " Matthew DeVore
2018-10-03 16:25 ` [PATCH v4 0/7] Clean up tests for test_cmp arg ordering and pipe placement Matthew DeVore
2018-10-03 16:25 ` [PATCH v4 1/7] t/README: reformat Do, Don't, Keep in mind lists Matthew DeVore
2018-10-05 6:15 ` Junio C Hamano
2018-10-05 14:57 ` Matthew DeVore
2018-10-03 16:26 ` [PATCH v4 2/7] Documentation: add shell guidelines Matthew DeVore
2018-10-05 16:48 ` Junio C Hamano
2018-10-05 18:21 ` Matthew DeVore
2018-10-03 16:26 ` [PATCH v4 3/7] tests: standardize pipe placement Matthew DeVore
2018-10-03 16:26 ` [PATCH v4 4/7] t/*: fix ordering of expected/observed arguments Matthew DeVore
2018-10-03 16:26 ` [PATCH v4 5/7] tests: don't swallow Git errors upstream of pipes Matthew DeVore
2018-10-05 16:48 ` Junio C Hamano
2018-10-05 17:54 ` Matthew DeVore
2018-10-05 18:12 ` Matthew DeVore
2018-10-03 16:26 ` [PATCH v4 6/7] t9109: " Matthew DeVore
2018-10-03 16:26 ` [PATCH v4 7/7] tests: order arguments to git-rev-list properly Matthew DeVore
2018-10-03 16:33 ` Matthew DeVore
2018-10-05 8:16 ` Junio C Hamano
2018-10-05 21:54 ` [PATCH v5 0/7] subject: Clean up tests for test_cmp arg ordering and pipe placement Matthew DeVore
2018-10-05 21:54 ` [PATCH v5 1/7] t/README: reformat Do, Don't, Keep in mind lists Matthew DeVore
2018-10-05 21:54 ` [PATCH v5 2/7] Documentation: add shell guidelines Matthew DeVore
2018-10-05 21:54 ` [PATCH v5 3/7] tests: standardize pipe placement Matthew DeVore
2018-10-05 21:54 ` [PATCH v5 4/7] t/*: fix ordering of expected/observed arguments Matthew DeVore
2018-10-05 21:54 ` [PATCH v5 5/7] tests: don't swallow Git errors upstream of pipes Matthew DeVore
2018-10-05 21:54 ` [PATCH v5 6/7] t9109: " Matthew DeVore
2018-10-05 21:54 ` [PATCH v5 7/7] tests: order arguments to git-rev-list properly Matthew DeVore
2018-10-06 23:53 ` [PATCH v5 0/7] subject: Clean up tests for test_cmp arg ordering and pipe placement Junio C Hamano
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=20180917163137.GB89942@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonathantanmy@google.com \
--cc=matvore@google.com \
--cc=peff@peff.net \
/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).