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
dashboard: unmark known-issues with low failure rates
I had initially added known issues fairly aggressively in order to use
them to reduce noise in 'greplogs -triage'. Now that we are using
'watchflakes' for triage, that noise reduction is no longer important
(the failures are already clustered to their respective known issues),
and having greyed-out cells on the dashboard makes new regressions too
easy to miss.
Concretely:
- golang/go#42212 is mostly specific to x/net at this point (as
golang/go#57841)
- There have been no failures matching golang/go#51001 since October.
- golang/go#52724 has been so rare lately that we hadn't yet added a
'watchflakes' pattern for it.
- There have been no failures matching golang/go#51443 since May.
- There have been no failures matching golang/go#53116 or
golang/go#53093 since I enabled 'watchflakes' for the builder in
December.
- The linux-amd64-perf builder seems to be passing consistently for
x/benchmarks and x/tools, so there is no need to refer to
golang/go#53538 to explain failures on it.
Change-Id: Ia16db2a23e5fa037a299f1f56fb26f1cf84521e1
Reviewed-on: https://go-review.googlesource.com/c/build/+/465156
Reviewed-by: Dmitri Shuralyov <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
Run-TryBot: Bryan Mills <[email protected]>
Auto-Submit: Bryan Mills <[email protected]>
TryBot-Result: Gopher Robot <[email protected]>
0 commit comments