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

Re: [PATCH v2 1/7] perf/aggregate: fix checking ENV{GIT_PERF_SUBSECTION}

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 28, 2017, 19:40 UTC
Message-ID
<xmqqpo6yk5dh.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20171226215908.425-2-chriscool@tuxfamily.org>
Christian Couder <christian.couder@gmail.com> writes:
Show 17 quoted lines
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
> ---
>  t/perf/aggregate.perl | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/t/perf/aggregate.perl b/t/perf/aggregate.perl
> index e401208488..769d418708 100755
> --- a/t/perf/aggregate.perl
> +++ b/t/perf/aggregate.perl
> @@ -70,7 +70,7 @@ if (not @tests) {
>  }
>  
>  my $resultsdir = "test-results";
> -if ($ENV{GIT_PERF_SUBSECTION} ne "") {
> +if (exists $ENV{GIT_PERF_SUBSECTION} and $ENV{GIT_PERF_SUBSECTION} ne "") {
>  	$resultsdir .= "/" . $ENV{GIT_PERF_SUBSECTION};
>  }

It appears that this is the only remaining environment variable reference that could trigger comparison between undef and "" that may be flagged by use of strict & warnings? A good change.

Previous: Christian CouderNext: Christian Couder
Message 6 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.