Host: chromeos15-row13a-rack1-host1
Host page: http://cros-full-0024.mtv.corp.google.com/afe/#tab_id=view_job&object_id=223241142
Job page: http://cros-full-0024.mtv.corp.google.com/afe/#tab_id=view_job&object_id=223034515


More than one hour after the device finished the test with failure, the test job is still hanging on ssh retries like:
-------------------------------------------
stderr:
ssh: connect to host chromeos15-row13a-rack1-host1 port 22: Connection timed out)
08/02 16:15:58.164 DEBUG|          ssh_host:0301| Running (ssh) 'portageq owners / mosys| sed -e "s/^[^\t].*/@@@ & @@@/" -e "s/^\t//"| tr \\n \\0 | xargs -0 -r stat -L -c "%a %A %n" 2>&1' from 'get_crashdumps|get_site_crashdumps|report_bug_from_crash|find_package_of|run|run_very_slowly'
08/02 16:17:01.416 DEBUG|             utils:0286| [stderr] ssh: connect to host chromeos15-row13a-rack1-host1 port 22: Connection timed out
08/02 16:17:01.417 WARNI| site_crashcollect:0405| Crash detection failed with: ('ssh timed out', * Command: 
    /usr/bin/ssh -a -x   -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 chromeos15-row13a-rack1-host1 "export LIBC_FATAL_STDERR_=1;
    if type \"logger\" > /dev/null 2>&1; then logger -tag \"autotest\"
    \"server[stack::report_bug_from_crash|find_package_of|run] ->
    ssh_run(portageq owners / mosys| sed -e \\\"s/^[^\\\\t].*/@@@ & @@@/\\\"
    -e \\\"s/^\\\\t//\\\"| tr \\\\\\\\n \\\\\\\\0 | xargs -0 -r stat -L -c
    \\\"%a %A %n\\\" 2>&1)\";fi; portageq owners / mosys| sed -e
    \"s/^[^\\t].*/@@@ & @@@/\" -e \"s/^\\t//\"| tr \\\\n \\\\0 | xargs -0 -r
    stat -L -c \"%a %A %n\" 2>&1"
Exit status: 255
Duration: 63.2359609604
-------------------------------------------

Huge number of mosys crashes are observed. Logs are at http://cros-full-0024.mtv.corp.google.com/results/223034515-chromeos-test/chromeos15-row13a-rack1-host1/debug/autoserv.DEBUG

Looks like provisioning job after the failed test is having problems too - http://cros-full-0024.mtv.corp.google.com/afe/#tab_id=view_job&object_id=223271495