Automatically wipe data from devices.

Automatically wipe data from devices.

Wiping data from the device for each build will keep the
INSTALL_FAILED_INSUFFICIENT_STORAGE error from happening.

Sleeping 75 seconds was determined by minimizing how much time was needed to
sleep for the provision and wipe to work on a Nexus 4.

BUG=335549
R=jbudorick@chromium.org, tonyg@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=273402

[navabi, 2014-05-27 22:53:21]

The CQ bit was checked by navabi@google.com

[navabi, 2014-05-27 22:53:31]

The CQ bit was unchecked by navabi@google.com

[navabi, 2014-05-28 20:55:00]

This CL is the fix of https://codereview.chromium.org/283363008/

That CL somehow got the .gitmodules messed up and kept failing bot update. In
the meantime jbudorick did some re-factoring.

[tonyg, 2014-05-28 20:57:32]

lgtm

[jbudorick, 2014-05-28 21:18:19]

lgtm with nit

After the refactor lands, we should be able to do provisioning entirely in
parallel, rather than the serial wipe, then parallel reboot, then serial
configuration structure we now have.

https://codereview.chromium.org/297233009/diff/40001/build/android/provision_...
File build/android/provision_devices.py (right):

https://codereview.chromium.org/297233009/diff/40001/build/android/provision_...
build/android/provision_devices.py:133:
.old_interface.Reboot(True).pFinish(None))
nit: this no longer needs to call pFinish, as the default parallel behavior is
now synchronous. I was planning to remove it from the call below.

[navabi, 2014-05-28 22:42:59]

https://codereview.chromium.org/297233009/diff/40001/build/android/provision_...
File build/android/provision_devices.py (right):

https://codereview.chromium.org/297233009/diff/40001/build/android/provision_...
build/android/provision_devices.py:138: device.WaitUntilFullyBooted(timeout=75)
if you look at the android tests try bot results, it shows that 75 seconds
timeout is not enough, even though it ends up working (presumably, because it
finishes close to 75 seconds).

I up'd the time out to 90 seconds and confirmed locally it does not happen.

[navabi, 2014-05-28 22:44:13]

The CQ bit was checked by navabi@google.com

[commit-bot: I haz the power, 2014-05-28 22:45:20]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/navabi@google.com/297233009/40002

[navabi, 2014-05-28 23:42:48]

Committed patchset #4 manually as r273402 (presubmit successful).