Short adb calls made by `AndroidDevice` controller should have timeouts

Open xpconanfan opened this issue 7 years ago • 1 comments

Most adb calls issued by AndroidDevice don't have any timeout today. This is causing problems in large device labs where there is a diverse collection of devices.

Sometimes devices get into a bad state, causing adb commands to get stuck. Because we don't have default timeout, this causes tests to hang forever.

All adb commands issued by AndroidDevice module should have a deterministic end time, unless it's a long running process.

Dec 08 '18 00:12 xpconanfan

#556

Feb 28 '19 19:02 xpconanfan