From: Thomas Gummerer <t.gummerer@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] perf-lib: remove old result files before running tests
Date: Fri, 22 Nov 2019 08:11:08 +0000 [thread overview]
Message-ID: <20191122081108.GA38815@cat> (raw)
In-Reply-To: <20191121102042.GA2611@sigill.intra.peff.net>
On 11/21, Jeff King wrote:
> But I wonder if it would be simpler to just always use the same file for
> the test result, overwriting it each time, and let the reader figure out
> the type. The aggregate script's get_times() already uses a regex to
> distinguish the two. That's enough for the two types we have, and we
> could later add a header line if it becomes necessary.
>
> Something like the patch below. That removes any confusion about cruft
> files being left behind, or which file should be preferred, etc.
Yeah, I like what you have below much more than what I had, thanks!
> The diff would be even smaller if we just kept calling it "times", but
> that's probably unnecessarily confusing.
Yup, I prefer a more readable end result to a small diff :)
> -Peff
>
> ---
> diff --git a/t/perf/aggregate.perl b/t/perf/aggregate.perl
> index 66554d2161..112fc23dbe 100755
> --- a/t/perf/aggregate.perl
> +++ b/t/perf/aggregate.perl
> @@ -219,13 +219,7 @@ sub print_default_results {
> for my $i (0..$#dirs) {
> my $d = $dirs[$i];
> my $base = "$resultsdir/$prefixes{$d}$t";
> - $times{$prefixes{$d}.$t} = [];
> - foreach my $type (qw(times size)) {
> - if (-e "$base.$type") {
> - $times{$prefixes{$d}.$t} = [get_times("$base.$type")];
> - last;
> - }
> - }
> + $times{$prefixes{$d}.$t} = [get_times("$base.result")];
> my ($r,$u,$s) = @{$times{$prefixes{$d}.$t}};
> my $w = length format_times($r,$u,$s,$firstr);
> $colwidth[$i] = $w if $w > $colwidth[$i];
> @@ -267,7 +261,7 @@ sub print_sorted_results {
> my ($prevr, $prevu, $prevs, $prevrev);
> for my $i (0..$#dirs) {
> my $d = $dirs[$i];
> - my ($r, $u, $s) = get_times("$resultsdir/$prefixes{$d}$t.times");
> + my ($r, $u, $s) = get_times("$resultsdir/$prefixes{$d}$t.result");
> if ($i > 0 and defined $r and defined $prevr and $prevr > 0) {
> my $percent = 100.0 * ($r - $prevr) / $prevr;
> push @evolutions, { "percent" => $percent,
> @@ -327,7 +321,7 @@ sub print_codespeed_results {
> my $commitid = $prefixes{$d};
> $commitid =~ s/^build_//;
> $commitid =~ s/\.$//;
> - my ($result_value, $u, $s) = get_times("$resultsdir/$prefixes{$d}$t.times");
> + my ($result_value, $u, $s) = get_times("$resultsdir/$prefixes{$d}$t.result");
>
> my %vals = (
> "commitid" => $commitid,
> diff --git a/t/perf/perf-lib.sh b/t/perf/perf-lib.sh
> index b58a43ea43..13e389367a 100644
> --- a/t/perf/perf-lib.sh
> +++ b/t/perf/perf-lib.sh
> @@ -214,7 +214,7 @@ test_perf_ () {
> else
> test_ok_ "$1"
> fi
> - "$TEST_DIRECTORY"/perf/min_time.perl test_time.* >"$base".times
> + "$TEST_DIRECTORY"/perf/min_time.perl test_time.* >"$base".result
> }
>
> test_perf () {
> @@ -223,7 +223,7 @@ test_perf () {
>
> test_size_ () {
> say >&3 "running: $2"
> - if test_eval_ "$2" 3>"$base".size; then
> + if test_eval_ "$2" 3>"$base".result; then
> test_ok_ "$1"
> else
> test_failure_ "$@"
next prev parent reply other threads:[~2019-11-22 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 18:50 [PATCH] perf-lib: remove old result files before running tests Thomas Gummerer
2019-11-20 4:12 ` Junio C Hamano
2019-11-20 8:00 ` Thomas Gummerer
2019-11-21 10:20 ` Jeff King
2019-11-22 8:11 ` Thomas Gummerer [this message]
2019-11-25 14:09 ` Jeff King
2019-11-25 17:04 ` Thomas Gummerer
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=20191122081108.GA38815@cat \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--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).