git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 3/7] perf/aggregate: implement codespeed JSON output

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 28, 2017, 19:47 UTC
Message-ID
<xmqqlghmk52j.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20171226215908.425-4-chriscool@tuxfamily.org>
Christian Couder <christian.couder@gmail.com> writes:
Show 6 quoted lines
> ...
> +sub print_codespeed_results {
> +	my ($results_section) = @_;
> +
> +	#use Data::Dumper qw/ Dumper /;
> +	#print Dumper(\@data);

Perhaps lose these. It is OK to keep the code live and hide it behind --debug or something, but it seems to me that you are done debugging it pretty much so...

> +	use JSON;

Have this at the top, perhaps? It's not like this would let us avoid loading JSON module when not doing codespeed (you need 'require' for that, right?).

Show 11 quoted lines
> +	print to_json(\@data, {utf8 => 1, pretty => 1}), "\n";
> +}
> +
>  binmode STDOUT, ":utf8" or die "PANIC on binmode: $!";
>  
> -print_default_results();
> +if ($codespeed) {
> +	print_codespeed_results($results_section);
> +} else {
> +	print_default_results();
> +}
Previous: Christian CouderNext: Christian Couder
Message 8 of 12 in “Codespeed perf results”
  1. 0/7 Codespeed perf resultsChristian Couder, Dec 26, 2017
  2. 2/7 perf/aggregate: refactor printing resultsChristian Couder, Dec 26, 2017
  3. 5/7 perf/run: learn about perf.codespeedOutputChristian Couder, Dec 26, 2017
  4. 7/7 perf/run: read GIT_TEST_REPO_NAME from perf.repoNameChristian Couder, Dec 26, 2017
  5. 1/7 perf/aggregate: fix checking ENV{GIT_PERF_SUBSECTION}Christian Couder, Dec 26, 2017
  6. Junio C HamanoDec 28, 2017
  7. 3/7 perf/aggregate: implement codespeed JSON outputChristian Couder, Dec 26, 2017
  8. Junio C HamanoDec 28, 2017
  9. 4/7 perf/run: add conf_opts argument to get_var_from_env_or_config()Christian Couder, Dec 26, 2017
  10. 6/7 perf/run: learn to send output to codespeed serverChristian Couder, Dec 26, 2017
  11. Christian CouderDec 26, 2017
  12. Junio C HamanoDec 28, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.