From: Jeff King <peff@peff.net>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Derrick Stolee <stolee@gmail.com>
Subject: Re: [PATCH] t/perf: use 'test_file_size' in more places
Date: Fri, 22 Nov 2024 03:28:05 -0500 [thread overview]
Message-ID: <20241122082805.GC1179306@coredump.intra.peff.net> (raw)
In-Reply-To: <50c1368630684f235548d2e9a68d4de3745b5fe6.1732220875.git.me@ttaylorr.com>
On Thu, Nov 21, 2024 at 03:29:24PM -0500, Taylor Blau wrote:
> The perf test suite prefers to use test_file_size over 'wc -c' when
> inside of a test_size block. One advantage is that accidentally writign
> "wc -c file" (instead of "wc -c <file") does not inadvertently break the
> tests (since the former will include the filename in the output of wc).
The use of "prefers" here confused me, because I did not think we used
test_file_size at all yet. I am certainly OK with arguing that we
should, but I was just confused on first read. Maybe you mean "s/perf//"?
Also, s/writign/writing/.
> I noticed while reviewing Stolee's --full-name-hash series that he added
> new test_size tests that use the test_file_size helper instead of "wc
> -c". I thought it would be good to clean up the existing uses of "wc -c"
> in the perf suite as a result, which is what this patch does.
Perhaps we should also touch the one in t/perf/README, which points
people using test_size to using "wc -c" in the first place?
-Peff
prev parent reply other threads:[~2024-11-22 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 20:29 [PATCH] t/perf: use 'test_file_size' in more places Taylor Blau
2024-11-22 0:47 ` Junio C Hamano
2024-11-22 8:28 ` Jeff King [this message]
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=20241122082805.GC1179306@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.com \
--cc=stolee@gmail.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