Understandably we don't want watchflakes running on trybots. Too many false positives from issues with unsubmitted CLs.
However, sometimes we see a flake we know is unrelated. In that case it's useful to be able to file an issue automatically instead of manually putting together all the stuff watchflakes does for us. We can probably share the code between such a tool and what watchflakes does to post to issues, just pointing the tool at a buildbucket build ID.
Understandably we don't want watchflakes running on trybots. Too many false positives from issues with unsubmitted CLs.
However, sometimes we see a flake we know is unrelated. In that case it's useful to be able to file an issue automatically instead of manually putting together all the stuff watchflakes does for us. We can probably share the code between such a tool and what watchflakes does to post to issues, just pointing the tool at a buildbucket build ID.