RPC Errors logged when nothing is wrong (context cancelled) |
|||
Issue description
I see this in the logs of successful swarming tasks:
[W 2019-01-14 16:50:19] RPC failed transiently. Will retry in 1s {"error":"failed to send request: context canceled", "host":"cr-buildbucket.appspot.com", "method":"UpdateBuild", "service":"buildbucket.v2.Builds", "sleepTime":"1s"}
[W 2019-01-14 16:50:19] RPC failed permanently: context canceled {"error":"context canceled", "host":"cr-buildbucket.appspot.com", "method":"UpdateBuild", "service":"buildbucket.v2.Builds"}
[E 2019-01-14 16:50:19] UpdateBuild RPC failed: UpdateBuild RPC failed: context canceled
[W 2019-01-14 16:50:19] RPC failed permanently: context canceled {"error":"context canceled", "host":"cr-buildbucket.appspot.com", "method":"UpdateBuild", "service":"buildbucket.v2.Builds"}
[E 2019-01-14 16:50:19] UpdateBuild RPC failed: UpdateBuild RPC failed: context canceled
It's distracting when trying to debug actual failures.
,
Jan 15
,
Jan 15
The log indicates something is wrong with the calling code though. I’ll take a look
,
Jan 15
Thanks for taking a look! I was debugging a swarming task that failed. I saw the errors and thought "hmm, maybe this is a clue as to what's going wrong". Then I opened a similar swarming task that had succeeded and when I saw the same error in the logs I knew it was probably not related to the swarming task failure. |
|||
►
Sign in to add a comment |
|||
Comment 1 by no...@chromium.org
, Jan 15