automatically detect if a timeout was due to late slave start |
|||
Issue descriptionIf a slave times out, it logs a message saying that it reached the master deadline. This can either be due to something taking too long on the slave, or due to the slave starting late, but we leave it to the person reading the log to figure that out. Instead, we could query cidb and compare the slave's start time with the master, and make it clear when that delay is unusually long that the problem was likely a failure to start.
,
May 24 2017
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
,
Mar 14 2018
This bug is very old, is Untriaged, and has no owner. If it is still relevant, reopen as Untriaged or open a new bug |
|||
►
Sign in to add a comment |
|||
Comment 1 by autumn@chromium.org
, May 23 2016Status: Available (was: Untriaged)