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

[PATCH v2 7/7] perf/run: read GIT_TEST_REPO_NAME from perf.repoName

From
Christian Couder <christian.couder@gmail.com>
Date
Dec 26, 2017, 21:59 UTC
Message-ID
<20171226215908.425-8-chriscool@tuxfamily.org>
In-Reply-To
<20171226215908.425-1-chriscool@tuxfamily.org>

The GIT_PERF_REPO_NAME env variable is used in the `aggregate.perl` script to set the 'environment' field in the JSON Codespeed output.

Let's make it easy to set this variable by setting it in a config file.

Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 t/perf/run | 3 +++
 1 file changed, 3 insertions(+)
diff --git a/t/perf/run b/t/perf/run
index ef56396546..1a100d6134 100755
--- a/t/perf/run
+++ b/t/perf/run
@@ -137,6 +137,9 @@ run_subsection () {
 	get_var_from_env_or_config "GIT_PERF_MAKE_COMMAND" "perf" "makeCommand"
 	get_var_from_env_or_config "GIT_PERF_MAKE_OPTS" "perf" "makeOpts"
 
+	get_var_from_env_or_config "GIT_PERF_REPO_NAME" "perf" "repoName"
+	export GIT_PERF_REPO_NAME
+
 	GIT_PERF_AGGREGATING_LATER=t
 	export GIT_PERF_AGGREGATING_LATER
 
-- 
2.15.1.361.g8b07d831d0
Previous: Christian CouderNext: Christian Couder
Message 4 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.