Issue #68790 added functionality to watchflakes to watch and report broken bots. A known limitation is that it's willing to report a given unique builder at most once, but it neither reopens¹ a previous issue nor opens a new one if it happens again after some time. Currently handling issue state in those cases is handled by manually reopening/filing a new issue (for example, see the recent recurrence in #74901 (comment)).
Filing this to track making watchflakes handle this automatically. @cagedmantis I couldn't find an existing tracking issue for this, but please deduplicate this if I missed something.
CC @golang/release, @thepudds.
¹ Issue #57632 may be related to the decision of whether it's better to re-open or file new issues. It may also matter how much time passed; reopening an issue so old that it's already been frozen is probably not what we want.
Issue #68790 added functionality to watchflakes to watch and report broken bots. A known limitation is that it's willing to report a given unique builder at most once, but it neither reopens¹ a previous issue nor opens a new one if it happens again after some time. Currently handling issue state in those cases is handled by manually reopening/filing a new issue (for example, see the recent recurrence in #74901 (comment)).
Filing this to track making watchflakes handle this automatically. @cagedmantis I couldn't find an existing tracking issue for this, but please deduplicate this if I missed something.
CC @golang/release, @thepudds.
¹ Issue #57632 may be related to the decision of whether it's better to re-open or file new issues. It may also matter how much time passed; reopening an issue so old that it's already been frozen is probably not what we want.