From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Patrick Steinhardt <ps@pks.im>,
Philippe Blain via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Victoria Dye <vdye@github.com>,
Neeraj Singh <neerajsi@microsoft.com>
Subject: Re: [PATCH 1/2] p7821: fix test_perf invocation for prereqs
Date: Sun, 13 Apr 2025 15:00:41 -0400 [thread overview]
Message-ID: <90b3f122-8b94-3b45-08e0-32af95f9cea5@gmail.com> (raw)
In-Reply-To: <Z-pD1puYT87YKAd4@pks.im>
Hi Patrick,
Le 2025-03-31 à 03:27, Patrick Steinhardt a écrit :
> On Fri, Mar 28, 2025 at 05:07:48PM +0000, Philippe Blain via GitGitGadget wrote:
>> diff --git a/t/perf/p7821-grep-engines-fixed.sh b/t/perf/p7821-grep-engines-fixed.sh
>> index 61e41b82cff..1d126c7b039 100755
>> --- a/t/perf/p7821-grep-engines-fixed.sh
>> +++ b/t/perf/p7821-grep-engines-fixed.sh
>> @@ -33,13 +33,13 @@ do
>> fi
>> if ! test_have_prereq PERF_GREP_ENGINES_THREADS
>> then
>> - test_perf $prereq "$engine grep$GIT_PERF_7821_GREP_OPTS $pattern" "
>> + test_perf "$engine grep$GIT_PERF_7821_GREP_OPTS $pattern" --prereq "$prereq" "
>> git -c grep.patternType=$engine grep$GIT_PERF_7821_GREP_OPTS $pattern >'out.$engine' || :
>> "
>> else
>> for threads in $GIT_PERF_GREP_THREADS
>> do
>> - test_perf PTHREADS,$prereq "$engine grep$GIT_PERF_7821_GREP_OPTS $pattern with $threads threads" "
>> + test_perf "$engine grep$GIT_PERF_7821_GREP_OPTS $pattern with $threads threads" --prereq "PTHREADS,$prereq" "
>> git -c grep.patternType=$engine -c grep.threads=$threads grep$GIT_PERF_7821_GREP_OPTS $pattern >'out.$engine.$threads' || :
>> "
>> done
>
> "$prereq" can be empty here as it depends on which regexp engine we're
> using. The second case you adapt already looked weird before because we
> potentially checked for "PTHREADS,",
Indeed, the reason why the second case did not fail even when built with PCRE (which
would not fail the first 'test_perf' since '$prereq' would be empty) is
that this second test (in fact the whole loop) is only reached if
GIT_PERF_GREP_THREADS is set in the environment, which sets the
PERF_GREP_ENGINES_THREADS prereq. So just running 'make perf' or
'./p7821-*' would not enter this part of the test.
> but the first case was correct
> before but is now potentially checking for the empty prerequisite. Does
> that actually work as expected?
Yes, it was correct when built with PCRE, but not without, as then
$prereq would not be empty. I did check that it works correctly
before sending the patch, both when built with and without PCRE.
Thank you for the review and also checking that the patch works correctly.
I just checked 'test_skip' which is the function that checks the prereq and
indeed and empty 'test_prereq' is treated as no prereq.
Cheers,
Philippe.
next prev parent reply other threads:[~2025-04-13 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 17:07 [PATCH 0/2] Two perf test fixes Philippe Blain via GitGitGadget
2025-03-28 17:07 ` [PATCH 1/2] p7821: fix test_perf invocation for prereqs Philippe Blain via GitGitGadget
2025-03-31 7:27 ` Patrick Steinhardt
2025-04-13 19:00 ` Philippe Blain [this message]
2025-03-28 17:07 ` [PATCH 2/2] p9210: fix 'scalar clone' when running from a detached HEAD Philippe Blain via GitGitGadget
2025-03-31 7:27 ` Patrick Steinhardt
2025-04-12 18:15 ` [PATCH v2 0/3] Two perf test fixes Philippe Blain via GitGitGadget
2025-04-12 18:15 ` [PATCH v2 1/3] p7821: fix test_perf invocation for prereqs Philippe Blain via GitGitGadget
2025-04-12 18:15 ` [PATCH v2 2/3] p9210: fix 'scalar clone' when running from a detached HEAD Philippe Blain via GitGitGadget
2025-04-12 18:15 ` [PATCH v2 3/3] p7821: fix instructions for testing with threads Philippe Blain via GitGitGadget
2025-04-14 21:48 ` Junio C Hamano
2025-04-13 2:50 ` [PATCH v2 0/3] Two perf test fixes Philippe Blain
2025-04-14 16:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=90b3f122-8b94-3b45-08e0-32af95f9cea5@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=neerajsi@microsoft.com \
--cc=ps@pks.im \
--cc=vdye@github.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).