git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Aryan Gupta via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Patrick Steinhardt [ ]" <ps@pks.im>,
	"Michal Suchánek [ ]" <msuchanek@suse.de>,
	"Jean-Noël AVILA [ ]" <jn.avila@free.fr>,
	aryangupta701 <garyan447@gmail.com>
Subject: Re: [PATCH] tests: modernize the test script t0010-racy-git.sh
Date: Thu, 29 Feb 2024 13:11:46 -0500	[thread overview]
Message-ID: <CAPig+cS5L=i2dYJnc+w5F-k0nSpOjdpqyk6T0gL7i0c01A40nQ@mail.gmail.com> (raw)
In-Reply-To: <pull.1675.git.1709209435242.gitgitgadget@gmail.com>

On Thu, Feb 29, 2024 at 7:24 AM Aryan Gupta via GitGitGadget
<gitgitgadget@gmail.com> wrote:
> From: aryangupta701 <garyan447@gmail.com>

The name in the "From:" header should match the name in the
"Signed-off-by:" trailer.

> Modernize the formatting of the test script to align with current
> standards and improve its overall readability.

The aim of this patch makes sense, but the implementation isn't quite correct.

> Signed-off-by: Aryan Gupta <garyan447@gmail.com>
> ---
> diff --git a/t/t0010-racy-git.sh b/t/t0010-racy-git.sh> @@ -16,19 +16,18 @@ do
>         files=$(git diff-files -p)
> -       test_expect_success \
> -       "Racy GIT trial #$trial part A" \
> -       'test "" != "$files"'
> +       test_expect_success 'Racy git trial #$trial part A' '
> +               test "" != "$files"
> +       '

The variable `trial` takes on values 0-4, and that value is meant to
appear in the test title as the script runs:

    Racy GIT trial #0 part A
    Racy GIT trial #0 part B
    Racy GIT trial #1 part A
    Racy GIT trial #1 part B
    ...

However, by changing the title from a double-quote string to a
single-quote string, you inhibit interpolation of the `trial` variable
into the title, hence the test titles instead show up as:

    Racy GIT trial #$trial part A
    Racy GIT trial #$trial part B
    Racy GIT trial #$trial part A
    Racy GIT trial #$trial part B

which is undesirable.

So, the title should continue using double-quotes, and not be changed
to single-quotes.

The other change, which fixes the style of the test's body, appears correct.

  reply	other threads:[~2024-02-29 18:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 12:23 [PATCH] tests: modernize the test script t0010-racy-git.sh Aryan Gupta via GitGitGadget
2024-02-29 18:11 ` Eric Sunshine [this message]
2024-02-29 21:57 ` [PATCH v2] " Aryan Gupta via GitGitGadget
2024-02-29 22:19   ` Eric Sunshine
2024-02-29 23:14   ` Junio C Hamano
2024-02-29 23:22     ` Eric Sunshine
2024-02-29 23:36       ` Junio C Hamano
2024-02-29 23:52         ` Eric Sunshine
2024-03-01  0:06           ` Eric Sunshine
2024-03-01  2:03             ` Junio C Hamano
2024-03-05 22:09   ` [PATCH v3] " Aryan Gupta via GitGitGadget
2024-03-05 23:02     ` Junio C Hamano
2024-03-06  9:14     ` [PATCH v4] " Aryan Gupta via GitGitGadget
2024-03-07 13:28       ` Christian Couder
2024-03-07 14:23         ` Aryan Gupta
2024-03-07 18:17           ` Junio C Hamano
2024-03-07 18:30             ` Junio C Hamano
2024-03-07 18:33               ` Aryan Gupta

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='CAPig+cS5L=i2dYJnc+w5F-k0nSpOjdpqyk6T0gL7i0c01A40nQ@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=garyan447@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=jn.avila@free.fr \
    --cc=msuchanek@suse.de \
    --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.
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).