phablet-flash sometimes fails saying "error: device not found"

[Paul Larson]

And before you ask, no, I'm not unplugging my device in the middle. :)

I'm getting this error on several devices in the lab. It doesn't happen every time, but more often than I'd like. It seems like perhaps adb doesn't like pushing things back to back in some cases. In the past, I've seen it return "protocol error" but now I seem to be getting that much less, and now seeing "error: device not found". I'll try to see if I can reproduce it locally to get more information like logcat and dmesg from the host to verify that nothing's actually getting disconnected.

One thing I also noticed is that it happened after trying to do a push right after enabling adb root. I think I've seen some cases where adb seems to briefly not see the device right after doing adb root. Perhaps all we need to do is separate that a bit more?

Here's a bit of the log from the phablet-flash session:
Storage requirements in /data satisfied
Setting up recovery rules
Pushing /home/ubuntu/Downloads/phablet-flash/115/raring-preinstalled-armel+maguro.zip to /sdcard/
4501 KB/s (28600806 bytes in 6.204s)
Pushing /home/ubuntu/Downloads/phablet-flash/115/raring-preinstalled-phablet-armhf.zip to /sdcard/
4685 KB/s (549448169 bytes in 114.526s)
restarting adbd as root
Pushing /tmp/tmp282uty to /cache/recovery/command
error: device not found
Error while executing adb -s 0149BD7E0A019003 push /tmp/tmp282uty /cache/recovery/command
Make sure the device is connected and viewable by running 'adb devices'
Ensure you have a root device, one which running 'adb root' does not return an error
Build step 'Execute shell' marked build as failure

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:phablet-tools at revision 91, scheduled for release in phablet-tools, milestone Unknown