faft: Fix the unplug USB method after imaging a test image to USB
Originally we call disable_usb_hub(), which disables all the USB ports,
including the build-in USB Ethernet, and causes some tests failed on
network failure. But not all the tests fail, some tests requiring USB
for recovery turn the USB hub on in the beginning.
Should call enable_usb_hub(host=True).
BUG=chromium-os:34395
TEST=run_remote_tests.sh --board daisy --remote dut -a "image=$IMAGE" \
TryFwB/control$
Change-Id: I146b3a5b44bf60e7cc1f01efe30ba31877f2a2ad
Reviewed-on: https://gerrit.chromium.org/gerrit/35690
Reviewed-by: Mike Truty <truty@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
diff --git a/server/cros/faftsequence.py b/server/cros/faftsequence.py
index b5fa5b1..ec7e36c 100644
--- a/server/cros/faftsequence.py
+++ b/server/cros/faftsequence.py
@@ -374,7 +374,7 @@
))
self.run_faft_sequence()
# 'Unplug' any USB keys in the servo from the dut.
- self.servo.disable_usb_hub()
+ self.servo.enable_usb_hub(host=True)
def clear_set_gbb_flags(self, clear_mask, set_mask):