As I test EC “suite:faft_ec”, firmware_UserRequestRecovery.ec_wp fails occasionally, even after 28 tests, test server retests it, it passes, but like to know the root cause,
For failure case:
06/21 12:12:27.807 INFO | mode_switcher:0097| ping timed out, try REC_ON
06/21 12:12:27.808 INFO | servo:0530| Setting power_state to 'rec'
06/21 12:12:31.564 DEBUG| test:0410| Test failed due to Setting 'power_state' to 'rec' :: Timeout waiting for response.. Exception log follows the after_iteration_hooks.
06/21 12:12:31.565 DEBUG| test:0415| Starting after_iteration_hooks for firmware_UserRequestRecovery.ec_wp
For pass case:
06/21 12:47:27.689 INFO | mode_switcher:0097| ping timed out, try REC_ON
06/21 12:47:27.690 INFO | servo:0530| Setting power_state to 'rec'
06/21 12:47:39.708 INFO | mode_switcher:0679| -[FAFT]-[ start wait_for_client ]---
06/21 12:47:39.709 DEBUG| utils:0215| Running 'ping '192.168.1.4' -w1 -c1'
For the failure case, DUT is not booted up from USB drive attached on servo V2 board (I need to press power button to proceed test), the Timeout is around 4s, why test server indicates timeout and what it is checking? Any suggestion?
Attached:
results-20-firmware_UserRequestRecovery.ec_wp.zip: failure case during “suite:faft_ec”;
results-29-firmware_UserRequestRecovery.ec_wp.zip: pass case as server retests after suite is done;
--
You received this message because you are subscribed to the Google Groups "faft users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.