From db032363916338fce1bb2f4b8b58672ef6b40383 Mon Sep 17 00:00:00 2001 From: Ed Santiago Date: Tue, 10 Jan 2023 06:41:27 -0700 Subject: [PATCH] logformatter: include base SHA, with history link This is to help me in my flake analysis. Scenario: I'm looking at recent flakes, and see Flake X. I know that Flake X was "fixed" two weeks ago. Did the fix not work? Or is this just one of those PRs that was created three weeks ago (or three months ago) and never rebased to pick up the fix? This adds a one-click way for me to tell. Signed-off-by: Ed Santiago --- contrib/cirrus/logformatter | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/contrib/cirrus/logformatter b/contrib/cirrus/logformatter index 4cea66774d..a9e332ad61 100755 --- a/contrib/cirrus/logformatter +++ b/contrib/cirrus/logformatter @@ -652,6 +652,11 @@ END_SYNOPSIS _a("{CIRRUS_BUILD_ID}", "https://cirrus-ci.com/build/{CIRRUS_BUILD_ID}"), _a("{CIRRUS_TASK_ID}", "https://cirrus-ci.com/task/{CIRRUS_TASK_ID}"))); + # BASE_SHA can tell us if our parent includes--or doesn't--a purported + # fix for a flake. Note that "commits", plural, links to a git history + # listing; if we used "commit", singular, that would be less useful. + $s .= _tr("Base commit", _a("{CIRRUS_BASE_SHA}", "https://{CIRRUS_REPO_CLONE_HOST}/{CIRRUS_REPO_FULL_NAME}/commits/{CIRRUS_BASE_SHA}")); + $s .= "\n"; return $s; }