1307241 - "unable to initialize device" is not scary enough

Status: RESOLVED WONTFIX

(Testing Graveyard :: Autophone, defect)

Description

[Geoff Brown [:gbrown]]

Autophone recently sent an email like:

  [autophone] autophone-3 unable to initialize device nexus-6p-3

  Hello, this is Autophone. Just to let you know, phone nexus-6p-3 failed to initialize due to args: adb -s 84B7N15A28009647 wait-for-device shell id; echo rc=$?, exitcode: None, stdout: , stderr: .

I noticed this failure on a superficial level, but dismissed it because I saw an email at the same time for an autophone-3 restart. The "unable to initialize device" email showed up first, so I parsed the situation as "device failed, autophone restarted, there were no more complaints, so all is well". Silly me.


I wonder if the email messaging could be improved. If we can reliably detect that a device needs attention, let's send a message that says that explicitly and/or "time to file a device intervention bug". If it's not possible, or difficult, to reliably detect that condition, can we use stronger wording or suggest action ("you should check on this device")?

Comment 1

[Bob Clary [:bc] (inactive)]

Autophone is going away. Resolving these to wontfix.