I'll note that, TBOOMK, there are no DUTs left in the lab
with the hotrod setting.  We're also actively exploring how
to prevent any more from being delivered into the lab.

That said, if we can get more extensive diagnosis of why
login failed it would be very helpful.  The "Timed out
going through login screen." error message is a pretty
common failure mode, and saying more in this case could
shorten debug cycles.

Here's my strawman proposal:  Alter the login screen flow
so that every dialog that can be presented has a name.
Make the name available to the Autotest code responsible
for walking through the flows.  When login fails, include
the on-screen dialog name in the error message.

I'm re-purposing this bug based on c#3.  Merely handling remora
DUTs is likely to have negative value, since we expect such DUTs
not to be in the lab.  OTOH, Handling "Timed out going through
login screen" in a diagnosable manner would be invaluable.

alemate@ can you look into this?

alemate@ Can you please update this bug with your findings? We haven't had any updates in the last 10 days.

Sorry, I didn't have time to look into this. I am currently investigating issue 567779 (in addition to OOBE).

Jacob, could you help finding owner for this?

 Issue 889078  is the equivalent bug about improving Tast's detection of this same issue.

Issue 888520 (about improving Chrome's logging about the login process) is also related.