FAFT: Compare the boot IDs to tell reboot too quickly
We expect DUT is offline after calling reboot action. Sometime (may be a
wrong behavior about timing), DUT boots very quickly and comes online soon.
Comparing the boot IDs can tell this scenario.
BUG=chromium-os:225022
TEST=run firmware_ConsecutiveBoot passed.
Change-Id: I5c48efa5f28287b2291260e2b0bd2277891ee9cf
Reviewed-on: https://gerrit.chromium.org/gerrit/49889
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Queue: 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 2d2942e..15b4a69 100644
--- a/server/cros/faftsequence.py
+++ b/server/cros/faftsequence.py
@@ -1469,8 +1469,9 @@
# Don't run reboot_action and firmware_action if no_reboot is True.
if not no_reboot:
+ boot_id = self._client.get_boot_id()
self._call_action(test['reboot_action'])
- self.wait_for_client_offline()
+ self.wait_for_client_offline(orig_boot_id=boot_id)
self._call_action(test['firmware_action'])
try: