faft-cr50: check /dev/tpm0 during reboot stress
On fizz we've seen some TPM flow control errors that result in /dev/tpm0
not getting created. This isn't necessarily a fizz specific issue. This
change adds a check for /dev/tpm0 after reboot just to see if we can
catch this issue during faft-cr50 nightly runs.
BUG=b:175650376
TEST=run on hatch and fizz
Change-Id: I1eee6d3f472b50a2ad4b3fba44b09b122dcbf05e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2602540
Tested-by: Mary Ruthven <mruthven@chromium.org>
Reviewed-by: Namyoon Woo <namyoon@chromium.org>
Commit-Queue: Namyoon Woo <namyoon@chromium.org>
Auto-Submit: Mary Ruthven <mruthven@chromium.org>
diff --git a/server/site_tests/firmware_Cr50DeepSleepStress/firmware_Cr50DeepSleepStress.py b/server/site_tests/firmware_Cr50DeepSleepStress/firmware_Cr50DeepSleepStress.py
index 0dc11ca..4090395 100644
--- a/server/site_tests/firmware_Cr50DeepSleepStress/firmware_Cr50DeepSleepStress.py
+++ b/server/site_tests/firmware_Cr50DeepSleepStress/firmware_Cr50DeepSleepStress.py
@@ -113,8 +113,13 @@
errors = []
for i in range(suspend_count):
+ if not self._dut_is_responsive():
+ raise error.TestFail('Unable to ssh into DUT after %d resets' %
+ i)
+ self.host.run('ls /dev/tpm0')
# Power off the device
- self.host.power_off_via_servo()
+ self.set_ap_off_power_mode('shutdown')
+
time.sleep(self.MIN_SUSPEND)
# Power on the device