FAFT: Add missing wait_for_kernel_up call when changing GBB flags
After changing GBB flags, if a reboot is needed, we must wait for the
client to come up again before continuing.
BUG=chrome-os-partner:29210
TEST=Run a test and see GBB changed
Change-Id: Ib99a681ff29baffcd4e94926842babcf85897090
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/202209
Reviewed-by: David Hendricks <dhendrix@chromium.org>
diff --git a/server/cros/faft/firmware_test.py b/server/cros/faft/firmware_test.py
index 30352f2..e3c5076 100644
--- a/server/cros/faft/firmware_test.py
+++ b/server/cros/faft/firmware_test.py
@@ -489,6 +489,7 @@
if ((gbb_flags ^ new_flags) & vboot.GBB_FLAG_FORCE_DEV_SWITCH_ON):
self.reboot_warm_trigger()
self.wait_dev_screen_and_ctrl_d()
+ self.wait_for_kernel_up()
def clear_set_gbb_flags(self, clear_mask, set_mask):
"""Clear and set the GBB flags in the current flashrom.