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
When closing scratch CLs, the maintner corpus doesn't get updated fast enough and it attempts to close the same CLs again, resulting in a 409 conflict:
2018/10/19 20:19:32 closing scratch CL https://golang.org/cl/140997 ...
2018/10/19 20:19:32 abandon scratch reviews: HTTP status 409 Conflict; change is abandoned
2018/10/19 20:19:32 HTTP status 409 Conflict; change is abandoned
2018/10/19 20:19:32 gopherbot ran in 1.745149115s
2018/10/19 20:19:32 sleeping 30s after previous error.
This error causes gopherbot to sleep for 30s as a result.
I think I've already seen code somewhere that uses Gerrit API in addition to maintner to confirm the "latest" state before taking some action. @bradfitz will probably remember where that was.
I suspect the fix for this can use a similar approach.
Note that this is different from #28226 in that the reported state isn't inconsistent, it's just not up to date.
dmitshur
changed the title
cmd/gopherbot: race condition in auto-closure of scratch CLs causing gopherbot to stall 30s
x/build/cmd/gopherbot: race condition in auto-closure of scratch CLs causing gopherbot to stall 30s
Oct 20, 2018
When closing scratch CLs, the maintner corpus doesn't get updated fast enough and it attempts to close the same CLs again, resulting in a 409 conflict:
This error causes gopherbot to sleep for 30s as a result.
This is related to #28226 /cc @dmitshur
The text was updated successfully, but these errors were encountered: