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
Watchflakes immediately reports any bot failure by creating an issue. However, bot maintainers find this too frequent, as they prefer to address issues after a bot has been consistently down or quarantined for a specific duration. We need to determine and implement a delay threshold before Watchflakes automatically generates an issue.
@golang/release
The text was updated successfully, but these errors were encountered:
Change https://go.dev/cl/659236 mentions this issue: cmd/watchflakes: only open issues bots that have been dead for 24-hours
dmitshur
added
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
Mar 19, 2025
Watchflakes immediately reports any bot failure by creating an issue. However, bot maintainers find this too frequent, as they prefer to address issues after a bot has been consistently down or quarantined for a specific duration. We need to determine and implement a delay threshold before Watchflakes automatically generates an issue.
@golang/release
The text was updated successfully, but these errors were encountered: