You were saying we can’t name it differently between event, but I’m not suggesting this, I was thinking of just changing the name everywhere.
We may be talking past each other right now though.
Looking at the implementation it may just be this diff:
diff --git a/.ci/metrics/metrics.py b/.ci/metrics/metrics.py
index a5ee893650d6..db5961e0c810 100644
--- a/.ci/metrics/metrics.py
+++ b/.ci/metrics/metrics.py
@@ -21,7 +21,7 @@ SCRAPE_INTERVAL_SECONDS = 5 * 60
# Lists the Github workflows we want to track. Maps the Github job name to
# the metric name prefix in grafana.
# This metric name is also used as a key in the job->name map.
-GITHUB_WORKFLOW_TO_TRACK = {"LLVM Premerge Checks": "github_llvm_premerge_checks"}
+GITHUB_WORKFLOW_TO_TRACK = {"Build & Test": "github_llvm_premerge_checks"}
# Lists the Github jobs to track for a given workflow. The key is the stable
# name (metric name) of the workflow (see GITHUB_WORKFLOW_TO_TRACK).
@@ -29,8 +29,8 @@ GITHUB_WORKFLOW_TO_TRACK = {"LLVM Premerge Checks": "github_llvm_premerge_checks
# name.
GITHUB_JOB_TO_TRACK = {
"github_llvm_premerge_checks": {
- "Linux Premerge Checks (Test Only - Please Ignore Results)": "premerge_linux",
- "Windows Premerge Checks (Test Only - Please Ignore Results)": "premerge_windows",
+ "Linux Checks (Test Only - Please Ignore Results)": "premerge_linux",
+ "Windows Checks (Test Only - Please Ignore Results)": "premerge_windows",
}
}
I suspect that would be enough to fix all the labels in the screenshot I posted in the initial message of this thread.
Similarly, these labels would look good on a pull-request here I believe:
would look like:
