You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a flag --known issue that associates issues with log entries based
on regexp matches. It's used like this:
--known-issue='#53456=TestDebugLines'
Which results in the check box for that log being pre-checked, and the
text '#53456' being added, which turns into a pretty link on GitHub.
It might be nice to group issues as well, but I didn't want to mess with
the chronological ordering.
For golang/go#52653.
Change-Id: If4615cd798ba72c1c1ee3cb43f1d1ad6d4319528
Reviewed-on: https://go-review.googlesource.com/c/build/+/425075
TryBot-Result: Gopher Robot <[email protected]>
Run-TryBot: Heschi Kreinick <[email protected]>
Auto-Submit: Heschi Kreinick <[email protected]>
Reviewed-by: Bryan Mills <[email protected]>
Copy file name to clipboardExpand all lines: cmd/greplogs/main.go
+10-1
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,7 @@ var (
46
46
fileRegexpsregexpList
47
47
failRegexpsregexpList
48
48
omitregexpList
49
+
knownIssuesregexpMap
49
50
50
51
flagDashboard=flag.Bool("dashboard", true, "search dashboard logs from fetchlogs")
51
52
flagMD=flag.Bool("md", true, "output in Markdown")
@@ -69,6 +70,7 @@ var brokenBuilders []string
69
70
funcmain() {
70
71
// XXX What I want right now is just to point it at a bunch of
71
72
// logs and have it extract the failures.
73
+
flag.Var(&knownIssues, "known-issue", "add an issue=regexp mapping; if a log matches regexp it will be categorized under issue. One mapping per flag.")
72
74
flag.Var(&fileRegexps, "e", "show files matching `regexp`; if provided multiple times, files must match all regexps")
73
75
flag.Var(&failRegexps, "E", "show only errors matching `regexp`; if provided multiple times, an error must match all regexps")
74
76
flag.Var(&omit, "omit", "omit results for builder names and/or revisions matching `regexp`; if provided multiple times, logs matching any regexp are omitted")
0 commit comments