chromeos6-row3-rack7-host1 in repair failure loop |
||||
Issue descriptiongoing to lock the dut and balance the pool https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/hosts/chromeos6-row3-rack7-host1/768835-repair/20180805102759/ START ---- repair timestamp=1525800487 localtime=May 08 10:28:07 GOOD ---- verify.servo_ssh timestamp=1525800489 localtime=May 08 10:28:09 GOOD ---- verify.brd_config timestamp=1525800490 localtime=May 08 10:28:10 GOOD ---- verify.ser_config timestamp=1525800491 localtime=May 08 10:28:11 GOOD ---- verify.job timestamp=1525800492 localtime=May 08 10:28:12 FAIL ---- verify.servod timestamp=1525800552 localtime=May 08 10:29:12 [Errno 104] Connection reset by peer START ---- repair.restart timestamp=1525800552 localtime=May 08 10:29:12 GOOD ---- verify.servo_ssh timestamp=1525800573 localtime=May 08 10:29:33 GOOD ---- verify.brd_config timestamp=1525800574 localtime=May 08 10:29:34 GOOD ---- verify.ser_config timestamp=1525800575 localtime=May 08 10:29:35 GOOD ---- verify.job timestamp=1525800576 localtime=May 08 10:29:36 FAIL ---- verify.servod timestamp=1525800636 localtime=May 08 10:30:36 [Errno 104] Connection reset by peer END FAIL ---- repair.restart timestamp=1525800636 localtime=May 08 10:30:36 START ---- repair.servo_reboot timestamp=1525800636 localtime=May 08 10:30:36 GOOD ---- verify.servo_ssh timestamp=1525800644 localtime=May 08 10:30:44 GOOD ---- verify.brd_config timestamp=1525800645 localtime=May 08 10:30:45 GOOD ---- verify.ser_config timestamp=1525800646 localtime=May 08 10:30:46 GOOD ---- verify.job timestamp=1525800647 localtime=May 08 10:30:47 FAIL ---- verify.servod timestamp=1525800707 localtime=May 08 10:31:47 [Errno 104] Connection reset by peer END FAIL ---- repair.servo_reboot timestamp=1525800707 localtime=May 08 10:31:47 GOOD ---- verify.update timestamp=1525800715 localtime=May 08 10:31:55 GOOD ---- verify.ssh timestamp=1525800736 localtime=May 08 10:32:16 GOOD ---- verify.power timestamp=1525800737 localtime=May 08 10:32:17 GOOD ---- verify.fwstatus timestamp=1525800737 localtime=May 08 10:32:17 FAIL ---- verify.good_au timestamp=1525800738 localtime=May 08 10:32:18 Last AU on this DUT failed START ---- repair.firmware timestamp=1525800738 localtime=May 08 10:32:18 FAIL ---- repair.firmware timestamp=1525800738 localtime=May 08 10:32:18 Firmware repair is not applicable to host chromeos6-row3-rack7-host1. END FAIL ---- repair.firmware timestamp=1525800738 localtime=May 08 10:32:18 GOOD ---- verify.devmode timestamp=1525800739 localtime=May 08 10:32:19 GOOD ---- verify.writable timestamp=1525800740 localtime=May 08 10:32:20 GOOD ---- verify.tpm timestamp=1525800741 localtime=May 08 10:32:21 GOOD ---- verify.ext4 timestamp=1525800742 localtime=May 08 10:32:22 GOOD ---- verify.rwfw timestamp=1525800743 localtime=May 08 10:32:23 FAIL ---- verify.python timestamp=1525800744 localtime=May 08 10:32:24 Python is missing; may be caused by powerwash FAIL ---- verify.cros timestamp=1525800811 localtime=May 08 10:33:31 command execution error * Command: /usr/bin/ssh -a -x -o ControlPath=/tmp/_autotmp_QoVjUissh-master/socket -o Protocol=2 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -l root -p 22 chromeos6-row3-rack7-host1 "export LIBC_FATAL_STDERR_=1; if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\" \"server[stack::verify|verify_software|run] -> ssh_run(update_engine_client --status)\";fi; update_engine_client --status" Exit status: 1 Duration: 58.5211029053
,
May 8 2018
repair ticket b/79421551
,
May 8 2018
have re-balanced the pool
,
May 8 2018
,
May 9 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by nxia@chromium.org
, May 8 2018