Description
We've been publishing minutes for various recurring discussions (proposal review, Go 2 review, compiler & runtime meeting notes). This issue is an attempt to apply the same pattern for builder triage.
We'll add a post here for the commands run throughout the week to triage failures on the Go build dashboard (https://build.golang.org).
For each day's triage, I first run fetchlogs to fetch the previous day's logs (and then some, because fetchlogs doesn't yet have a date flag). Then, I use greplogs to identify failures since the previous run, excluding known-bad commits and known-flaky builders.
greplogs --triage outputs Markdown containing GitHub task lists. Entries that have been triaged will be checked off the corresponding post.
―
The commands to perform a typical triage run look like:
$ fetchlogs -branch=release-branch.go1.19,release-branch.go1.18
$ fetchlogs -n 1024 -repo all
$ greplogs --triage --since=$LAST_TRIAGE_DATE
fetchlogs may take several minutes to finish; greplogs should be faster.
If the greplogs output has too much noise (such as due to a large build break or malfunctioning builder), use the --omit, --since, and/or --before flags to prune it down. When you've got it down to a manageable size, paste the Markdown output from greplogs into a new comment on this issue.
Then, check off the failures from the list as you triage them. (It's ok to leave entries unchecked if you haven't gotten to them yet, but try to finish the last run before moving on to a new one.)