In Gerrit, I first run TryBots on a CL (mine or someone else)'s with "Reply" and then I click the "+1" button next to "Run-TryBot". This runs TryBots.
The TryBots run, but with errors that look probably unrelated to the CL.
Since I ran TryBots by clicking "+1" in the reply pane, "obviously" the way to do this is to reset the value to zero (the "0" is not dimmed, therefore this is permitted, right?) and then clock "+1" again (worked once, why not again?).
What did you expect to see?
A second run of the TryBots.
What did you see instead?
NOT a second run of the TryBots.
I understand that what's actually missing is that (1) we've decided that people need special permission for this operation (2) I lack this permission (3) I should know this by noticing the absence of a button that I never knew existed.
I think we ought to fix the policy unless there's a really good reason not to let people do this, and if we can't fix the policy, we need to fix the UI to avoid people intuiting an unproductive way to spend their time not rerunning TryBots. What I actually want is "Rerun failed TryBots" and ideally someone is monitoring that to infer flakiness over time.
My workaround for this is to attempt to do the rerun by hand using a gomote, which is its own fiasco of stale documentation and read-all-the-docs-maybe-you'll-find-a-hint (oops, the hint has gone stale also).
The text was updated successfully, but these errors were encountered:
Thank you for reporting this @dr2chase and providing detail. I agree this is a usability problem. If someone has permissions to start trybots, it seems reasonable that they should also have the permission to restart them.
We should investigate what is a good way to resolve this issue.
Issue #38235 is related, and should also be resolved to improve the usability of trybot restarts.
Document the existing process for restarting a TryBot run (i.e., it requires pressing the trash can icon and deleting the TryBot-Result vote), if it's not already documented somewhere. That way, we can at least point people to it when they run into this issue.
Consider what more, if anything, needs to be done to improve the usability.
I just ran into the same issue trying to figure out how to rerun failed trybots. I poked around. I did see the trash icon in a hover, but it did not occur to me that it would help. I expected to see something like a looping arrow. After reading this issue I removed TryBot-Result-1. It doesn't seem to work. https://go-review.googlesource.com/c/vscode-go/+/394136
Here's the recipe I use, that has worked in the last month for me:
(1) you have to wait several minutes from the last TryBot-Result vote or else the coordinator gets confused
(2) you have to, in order, remove any previous Run-TryBot+1 votes and then TryBot-Result (click the trash can)
(3) you have to add the TRY= comment in the same reply as the new Run-TryBot+1 vote.
For a slowbot, include e.g.
to request a builder. (but linux-amd64 always runs).