Report RPC timeouts with meaningful error messages
Reported by
jrbarnette@chromium.org,
Dec 8 2016
|
|||
Issue description
When an Autotest RPC call times out in RetryingAFE or
RetryingTKO, it produces an error message along these
lines:
Traceback (most recent call last):
[ ... much tracing back ... ]
File "/usr/local/autotest/site-packages/chromite/lib/timeout_util.py", line 62, in kill_us
raise TimeoutError(error_message % {'time': max_run_time})
TimeoutError: Timeout occurred- waited 1800 seconds.
It would be better to say explicitly what timed out. Minimally,
a message like this:
RPC to host X timed out after %d seconds
Better still might be to mention which call timed out:
RPC 'get_fubar' to host X timed out after %d seconds
,
Feb 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 15 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by autumn@chromium.org
, Dec 13 2016