EVE NVME device at Cassandra stresslab: faft-setup is consistently failing. Failed to start XMLRPC server. |
|||
Issue description
Device location: Host chromeos1-row1-rack1-host3
pool: faft-test
Type of hardware : eve NVME
Chrome OS Version : 9765.32.0 (Official Build) dev-channel eve test
BIOS VERSION : Google_Eve.9584.76.0 / Google_Eve.9584.76.0
EC Version : eve_v1.1.6566-81013dc32 / eve_v1.1.6566-81013dc32
Begalbone info:
OS: 9672.0.0 (Official Build) dev-channel beaglebone_servo test
CHROMEOS_RELEASE_APPID={1BB651DD-C762-3FCF-2A66-CEB4C1096BB1}
CHROMEOS_BOARD_APPID={1BB651DD-C762-3FCF-2A66-CEB4C1096BB1}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
What steps will reproduce the problem?
(1) Make sure servod running without any errors-
chromeos1-row1-rack1-host3-servo
sudo start servod BOARD=eve
(2) Kick off the faft-setup test at cassandra stress lab.
(3) faft-setup should be passed successfully
What happens instead?
faft-setup is failing with below error:
08/18 11:39:04.567 WARNI| retry:0183| Retrying in 0.934047 seconds...
08/18 11:39:05.507 WARNI| retry:0228| <class 'httplib.BadStatusLine'>('')
08/18 11:39:05.508 WARNI| retry:0183| Retrying in 1.086586 seconds...
08/18 11:39:06.605 WARNI| retry:0228| <class 'httplib.BadStatusLine'>('')
08/18 11:39:06.605 WARNI| retry:0183| Retrying in 1.093659 seconds...
08/18 11:39:07.709 WARNI| retry:0228| <class 'httplib.BadStatusLine'>('')
08/18 11:39:07.709 ERROR|rpc_server_tracker:0201| Failed to start XMLRPC server.
,
Aug 18 2017
,
Aug 29 2017
Infra team pushed-to-prod the following CL https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/616102. FAFT-setup is passing now with no errors on EVE NVME at cassandra.
,
Aug 29 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by venkatar...@chromium.org
, Aug 18 2017