commit 51ef2e16b72c271f55929df287f23a6b7382eff3
author Tom Wai-Hong Tam <waihong@chromium.org> Fri Jul 27 15:04:12 2012 +0800
committer Gerrit <chrome-bot@google.com> Fri Jul 27 09:29:40 2012 -0700
tree 88c35ec2ca9802deaa58c26de7b3683f665e9121
parent a5e48a48ad193c25c36f14f5e331050094702aee

faft: Clear the short delay GBB flag before running DevScreenTimeout FAFT

The short delay GBB flag is disabled in the release firmware. So the
DevScreenTimeout should only check this release case.

Clear this flag if presented before running the test.

BUG=chrome-os-partner:9190
TEST=run firmware_DevScreenTimeout on Link passed.

Change-Id: I4489913eadb9efe81a13121495629cb9316e5c8f
Reviewed-on: https://gerrit.chromium.org/gerrit/28583
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>

server/cros/faftsequence.py

diff --git a/server/cros/faftsequence.py b/server/cros/faftsequence.py
index 4d639fe..fc9f13c 100644
--- a/server/cros/faftsequence.py
+++ b/server/cros/faftsequence.py
@@ -102,6 +102,9 @@
     # Delay between sending keystroke to firmware
     FIRMWARE_KEY_DELAY = 0.5
 
+    # The developer screen timeouts fit our spec.
+    DEV_SCREEN_TIMEOUT = 30
+
     CHROMEOS_MAGIC = "CHROMEOS"
     CORRUPTED_MAGIC = "CORRUPTD"