From: Derrick Stolee <derrickstolee@github.com>
To: Jeff King <peff@peff.net>, git@vger.kernel.org
Cc: Neeraj Singh <neerajsi@microsoft.com>
Subject: Re: [PATCH] perf-lib: fix missing test titles in output
Date: Thu, 16 Jun 2022 09:03:37 -0400 [thread overview]
Message-ID: <6671fd2c-ffcb-6278-494f-2d3cfe4c36d1@github.com> (raw)
In-Reply-To: <YqrXLO5oMYeOr2PB@coredump.intra.peff.net>
On 6/16/2022 3:09 AM, Jeff King wrote:
> Commit 5dccd9155f (t/perf: add iteration setup mechanism to perf-lib,
> 2022-04-04) modified the parameter parsing of test_wrapper() such that
> the test title was no longer in $1, and is instead in $test_title_.
>
> We correctly pass the new variable to the code which outputs the title
> to the log, but missed the spot in test_wrapper() where the title is
> written to the ".descr" file which is used to produce the final output
> table. As a result, all of the titles are missing from that table (or
> worse, using whatever was left in $1):
>
> $ ./p0000-perf-lib-sanity.sh
> [...]
> Test this tree
> ------------------------------
> 0000.1: 0.01(0.01+0.00)
> 0000.2: 0.01(0.00+0.01)
> 0000.4: 0.00(0.00+0.00)
> 0000.5: true 0.00(0.00+0.00)
> 0000.7: 0.00(0.00+0.00)
> 0000.8: 0.00(0.00+0.00)
Yikes!
> After this patch, we get the pre-5dccd9155f output:
>
> Test this tree
> --------------------------------------------------------------------------
> 0000.1: test_perf_default_repo works 0.00(0.00+0.00)
> 0000.2: test_checkout_worktree works 0.01(0.00+0.01)
> 0000.4: export a weird var 0.00(0.00+0.00)
> 0000.5: éḿíẗ ńöń-ÁŚĆÍÍ ćḧáŕáćẗéŕś 0.00(0.00+0.00)
> 0000.7: important variables available in subshells 0.00(0.00+0.00)
> 0000.8: test-lib-functions correctly loaded in subshells 0.00(0.00+0.00)
Good catch. LGTM.
-Stolee
next prev parent reply other threads:[~2022-06-16 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 7:09 [PATCH] perf-lib: fix missing test titles in output Jeff King
2022-06-16 13:03 ` Derrick Stolee [this message]
2022-06-16 19:51 ` Neeraj Singh (WINDOWS-SFS)
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=6671fd2c-ffcb-6278-494f-2d3cfe4c36d1@github.com \
--to=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=neerajsi@microsoft.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.
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).