/tmp/test_that_results_TiP_Ok/results-1-firmware_FAFTSetup [ FAILED ]/tmp/test_that_results_TiP_Ok/results-1-firmware_FAFTSetup ERROR: Unhandled Fault: <Fault 1: "<type 'exceptions.AttributeError'>:'module' object has no attribute 'fdpexpect'">/tmp/test_that_results_TiP_Ok/results-1-firmware_FAFTSetup/firmware_FAFTSetup [ FAILED ]/tmp/test_that_results_TiP_Ok/results-1-firmware_FAFTSetup/firmware_FAFTSetup ERROR: Unhandled Fault: <Fault 1: "<type 'exceptions.AttributeError'>:'module' object has no attribute 'fdpexpect'">/tmp/test_that_results_TiP_Ok/results-1-firmware_FAFTSetup/firmware_FAFTSetup 01/27 01:33:03.177 ERROR| base_utils:0268| [stderr] mux_client_request_session: read from master failed: Broken pipe/tmp/test_that_results_TiP_Ok/results-1-firmware_FAFTSetup/firmware_FAFTSetup 01/27 01:33:03.244 ERROR| base_utils:0268| [stderr] Warning: Permanently added '192.168.0.100' (RSA) to the list of known hosts./tmp/test_that_results_TiP_Ok/results-1-firmware_FAFTSetup/firmware_FAFTSetup 01/27 01:33:03.376 ERROR| base_utils:0268| [stderr] Warning: Permanently added '192.168.0.100' (RSA) to the list of known hosts.
-----------------------------------------------------------------------------------------Total PASS: 0/2 (0%)
--
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<mailto:faft-users+un...@chromium.org>.
I am guessing that there is a problem with the installed version of the python implementation of the “expect” language (called “pexpect”) or with the running copy of servod which uses it.
This is based just on the word ‘fdpexpect’ in your message.
So at this point the next questions are
1) Are you running the servod inside the cros_sdk environment (You must)?
2) Are you running servod with the correct “—board=” parameter?
3) Are there any informative messages you see when you start up servod, in particular ones about missing files?
a. If this is a new board type, you might be better off telling servod that it is a closely related board until you know enough to construct the needed files.
4) Do you have a servo card? Is it a version 2? Do you haveit connected to the Device Under Test (DUT) via a ribbon cable to the V2 connection, and to your linux host via a USB cable to the host_in port?
When you finish a run of “test_that –board=WHATEVER 192.168.0.100 firmware_FAFTSetup” the last line should tell you that it has put the results in /tmp/test_that_results_XXXXXX and made /tmp/test_that_latest point to it. Inside that tmp directory there are additional files which *might* help you (and us) debug your problems. You are definitely doing the right thing concentrating on getting FAFTSetup working as a first step.
To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org<mailto:faft-users+...@chromium.org>.
--
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.