firmware_Cr50DeviceState: trigger S0 before cleanup

Make sure to trigger S0 before cleanup. Tests seem to run faster if the
DUT can respond to pings before cleanup. Trigger s0 before cleanup so
the test runs faster.

BUG=none
BRANCH=none
TEST=run with TOT

Change-Id: Ie47db32fe5f8778bdba20ee8a81ad3f105bc8f25
Signed-off-by: Mary Ruthven <mruthven@google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/1310855
Tested-by: Mary Ruthven <mruthven@chromium.org>
Reviewed-by: Kevin Shelton <kmshelton@chromium.org>
diff --git a/server/site_tests/firmware_Cr50DeviceState/firmware_Cr50DeviceState.py b/server/site_tests/firmware_Cr50DeviceState/firmware_Cr50DeviceState.py
index 1149040..f81538a 100644
--- a/server/site_tests/firmware_Cr50DeviceState/firmware_Cr50DeviceState.py
+++ b/server/site_tests/firmware_Cr50DeviceState/firmware_Cr50DeviceState.py
@@ -416,6 +416,7 @@
             logging.info('Current setup only supports test with ccd %sabled.',
                     'en' if self.ccd_enabled else 'dis')
 
+        self.trigger_s0()
         if self.all_errors:
             raise error.TestFail('Unexpected Device State: %s' %
                     self.all_errors)