FAFTSetup errors

[Uma Mondal]

Recently the FAFTSetup test generates the following errors consistently. Can anybody point me to the right direction:-

/tmp/test_that_results_fxNMJm/results-1-firmware_FAFTSetup                    [  FAILED  ]
/tmp/test_that_results_fxNMJm/results-1-firmware_FAFTSetup                      ERROR: Unhandled Fault: <Fault 1: '<type \'exceptions.Exception\'>:method "ctrl_d" is not supported'>
/tmp/test_that_results_fxNMJm/results-1-firmware_FAFTSetup/firmware_FAFTSetup [  FAILED  ]
/tmp/test_that_results_fxNMJm/results-1-firmware_FAFTSetup/firmware_FAFTSetup   ERROR: Unhandled Fault: <Fault 1: '<type \'exceptions.Exception\'>:method "ctrl_d" is not supported'>

[Yusuf Mohsinally]

Uma,

This error seems to originate here.

It looks like your code repos are probably out of date.

Please make sure that you do not have any local changes and you repo  sync and rebuild your packages. Here are some commands that should help:

cros_workon list-all

repo sync

build_packages --board=<BOARD>

If you continue to have issues please zip up the whole logs directory and send them to us.

Thanks,

Yusuf

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

[Shawn N]

Thanks Yusuf for checking. I think Uma may not have access to that code search link, but your suggestions are still valid. Also, make sure to run "sudo emerge hdctools" and restart servod after doing repo sync.

[Ajit Tapkir]

FAFTSetup test passed on my old repo.

I have created fresh repo and followed the steps mentioned on http://www.chromium.org/for-testers/faft

FAFTSetup test is failing on newly created repo.
I am using Test Image, EC & BIOS from Chrome OS Partners.

03:46:29 INFO | autoserv| Expected 'mainfw_type' value 'recovery' but got 'normal'
I have attached complete logs of FAFTSetup.

-----------------------------------------------------------------------------------------
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup                    [  FAILED  ]
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup                      FAIL: Not succeed: calling <bound method FAFTCheckers.crossystem_checker of <autotest_lib.server.cros.faft.utils.faft_checkers.FAFTCheckers object at 0x38baad0>> with args ({'mainfw_type': 'recovery'},) returning False
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup [  FAILED  ]
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   FAIL: Not succeed: calling <bound method FAFTCheckers.crossystem_checker of <autotest_lib.server.cros.faft.utils.faft_checkers.FAFTCheckers object at 0x38baad0>> with args ({'mainfw_type': 'recovery'},) returning False
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:45:01.227 ERROR|base_utils:0238| [stderr] mux_client_request_session: read from master failed: Broken pipe
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:45:01.444 ERROR|base_utils:0238| [stderr] Warning: Permanently added '192.168.1.18' (RSA) to the list of known hosts.
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:45:01.675 ERROR|base_utils:0238| [stderr] Warning: Permanently added '192.168.1.18' (RSA) to the list of known hosts.
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:45:24.982 ERROR|base_utils:0238| [stderr] mux_client_request_session: read from master failed: Broken pipe
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:45:25.078 ERROR|base_utils:0238| [stderr] Warning: Permanently added '192.168.1.18' (RSA) to the list of known hosts.
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:45:25.168 ERROR|base_utils:0238| [stderr] Warning: Permanently added '192.168.1.18' (RSA) to the list of known hosts.
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:46:57.245 ERROR|base_utils:0238| [stderr] mux_client_request_session: read from master failed: Broken pipe
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:46:57.354 ERROR|base_utils:0238| [stderr] Warning: Permanently added '192.168.1.18' (RSA) to the list of known hosts.
/tmp/test_that_results_vDN_8n/results-1-firmware_FAFTSetup/firmware_FAFTSetup   08/08 01:46:57.592 ERROR|base_utils:0238| [stderr] Warning: Permanently added '192.168.1.18' (RSA) to the list of known hosts.
-----------------------------------------------------------------------------------------
Total PASS: 0/2 (0%)

Traceback (most recent call last):
  File "/build/peach_pi/usr/local/build/autotest/site_utils/test_that.py", line 881, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/build/peach_pi/usr/local/build/autotest/site_utils/test_that.py", line 877, in main
    return _main_for_local_run(argv, arguments)
  File "/build/peach_pi/usr/local/build/autotest/site_utils/test_that.py", line 837, in _main_for_local_run
    arguments, autotest_path, argv)
  File "/build/peach_pi/usr/local/build/autotest/site_utils/test_that.py", line 762, in _perform_run_from_autotest_root
    os.symlink(link_target, _LATEST_RESULTS_DIRECTORY)
OSError: [Errno 17] File exists


During test i am also getting stderr for runlevel, flashrom, flash_ec

3:44:25 INFO | autoserv| [stderr] sudo: runlevel: command not found
03:44:25 INFO | autoserv| Command <sudo -n runlevel> failed, rc=1, Command returned non-zero exit status
03:44:25 INFO | autoserv| * Command:
03:44:25 INFO | autoserv| sudo -n runlevel
03:44:25 INFO | autoserv| Exit status: 1
03:44:25 INFO | autoserv| Duration: 0.0146310329437
03:44:25 INFO | autoserv|
03:44:25 INFO | autoserv| stderr:
03:44:25 INFO | autoserv| sudo: runlevel: command not found
03:44:25 INFO | autoserv| Applying an update to the servo host, if necessary.
03:44:25 INFO | autoserv| Not attempting an update, either localhost is not running chromeos or we cannot find enough information about the host.
03:44:25 INFO | autoserv| Verifying if servo config file exists.
03:44:25 INFO | autoserv| Command <sudo -n test -f /var/lib/servod/config> failed, rc=1, Command returned non-zero exit status
03:44:25 INFO | autoserv| * Command:
03:44:25 INFO | autoserv| sudo -n test -f /var/lib/servod/config
03:44:25 INFO | autoserv| Exit status: 1
03:44:25 INFO | autoserv| Duration: 0.0345919132233
03:44:25 INFO | autoserv|
03:44:25 INFO | autoserv| Ignoring servo config check failure, either localhost is not running chromeos or we cannot find enough information about the host.
03:44:25 INFO | autoserv| Verifying servo host localhost with sanity checks.
03:44:25 INFO | autoserv| Setting dut_hub_pwren to on
03:44:25 INFO | autoserv| Setting usb_mux_oe1 to on
03:44:25 INFO | autoserv| Setting prtctl4_pwren to off
03:44:28 INFO | autoserv| Will execute on servo host: which flashrom
03:44:28 INFO | autoserv| [stderr] which: no flashrom in (/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin)
03:44:28 INFO | autoserv| Command <sudo -n which flashrom> failed, rc=1, Command returned non-zero exit status
03:44:28 INFO | autoserv| * Command:
03:44:28 INFO | autoserv| sudo -n which flashrom
03:44:28 INFO | autoserv| Exit status: 1
03:44:28 INFO | autoserv| Duration: 0.0292499065399
03:44:28 INFO | autoserv|
03:44:28 INFO | autoserv| stderr:
03:44:28 INFO | autoserv| which: no flashrom in (/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/opt/bin)
03:44:28 INFO | autoserv| Ignoring exception when verify required bins : flashrom
03:44:28 INFO | autoserv| Will execute on servo host: which flash_ec
03:44:28 INFO | autoserv| Sanity checks pass on servo host localhost