From: Junio C Hamano <gitster@pobox.com>
To: Johannes Altmanninger <aclopte@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"René Scharfe" <l.s.r@web.de>, "Git List" <git@vger.kernel.org>,
"Jeff King" <peff@peff.net>
Subject: Re: [PATCH RESEND] t/perf: do not run tests in user's $SHELL
Date: Mon, 20 Dec 2021 13:06:15 -0800 [thread overview]
Message-ID: <xmqqilvjugu0.fsf@gitster.g> (raw)
In-Reply-To: <20211220131121.mdxe7o6p3y25fzbw@gmail.com> (Johannes Altmanninger's message of "Mon, 20 Dec 2021 14:11:21 +0100")
Johannes Altmanninger <aclopte@gmail.com> writes:
> On Mon, Dec 20, 2021 at 12:56:58PM +0100, Ævar Arnfjörð Bjarmason wrote:
>>
>> On Mon, Dec 20 2021, René Scharfe wrote:
>>
>> > From: Johannes Altmanninger <aclopte@gmail.com>
>> >
>> > The environment variable $SHELL is usually set to the user's
>> > interactive shell. We never use that shell for build and test scripts
>> > because it might not be a POSIX shell.
>> >
>> > Perf tests are run inside $SHELL via a wrapper defined in
>> > t/perf/perf-lib.sh. Use $TEST_SHELL_PATH like elsewhere.
>> >
>> > Signed-off-by: Johannes Altmanninger <aclopte@gmail.com>
>> > Acked-by: Jeff King <peff@peff.net>
>> > ---
>> > Original submission:
>> > https://lore.kernel.org/git/20211007184716.1187677-1-aclopte@gmail.com/
>>
>> This LGTM & I think it could be picked up as-is.
>>
>> Just a nit in case af a re-roll. I think it would help to summarize the
>> history a bit per
>> https://lore.kernel.org/git/YV+1%2F0b5bN3o6qRG@coredump.intra.peff.net/. I.e. something
>> like:
>>
>> In 342e9ef2d9e (Introduce a performance testing framework, 2012-02-17)
>> when t/perf was introduced the TEST_SHELL_PATH was not part of
>> GIT-BUILD-OPTIONS.
>
> (but SHELL_PATH was, which is what we should have used back then)
>
>> That was added later in 3f824e91c84 (t/Makefile:
>> introduce TEST_SHELL_PATH, 2017-12-08). We will always have that
>> available in perf-lib.sh since test-lib.sh will load it before this code
>> is executed.
>
> yes that's a good thing to point out
Care to redo the patch in a final form, then?
Thanks.
>
>>
>> > t/perf/perf-lib.sh | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/t/perf/perf-lib.sh b/t/perf/perf-lib.sh
>> > index 780a7402d5..407252bac7 100644
>> > --- a/t/perf/perf-lib.sh
>> > +++ b/t/perf/perf-lib.sh
>> > @@ -161,7 +161,7 @@ test_run_perf_ () {
>> > test_cleanup=:
>> > test_export_="test_cleanup"
>> > export test_cleanup test_export_
>> > - "$GTIME" -f "%E %U %S" -o test_time.$i "$SHELL" -c '
>> > + "$GTIME" -f "%E %U %S" -o test_time.$i "$TEST_SHELL_PATH" -c '
>> > . '"$TEST_DIRECTORY"/test-lib-functions.sh'
>> > test_export () {
>> > test_export_="$test_export_ $*"
>>
next prev parent reply other threads:[~2021-12-20 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 11:05 [PATCH RESEND] t/perf: do not run tests in user's $SHELL René Scharfe
2021-12-20 11:56 ` Ævar Arnfjörð Bjarmason
2021-12-20 13:11 ` Johannes Altmanninger
2021-12-20 21:06 ` Junio C Hamano [this message]
2021-12-25 7:47 ` Johannes Altmanninger
2021-12-25 8:16 ` [PATCH v2] " Johannes Altmanninger
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=xmqqilvjugu0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=aclopte@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
--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.
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).