This wizpig-paladin run failed:
    https://luci-milo.appspot.com/buildbot/chromeos/wizpig-paladin/1808

The reason was that this test ran into trouble:
    http://cautotest-prod.corp.google.com/afe/#tab_id=view_job&object_id=163035372

The `dut-status` command shows this history around the test failure:
    2017-12-16 19:31:34  -- http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/163036581-chromeos-test/
    2017-12-16 19:19:15  OK http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack8-host13/1490029-provision/
    2017-12-16 17:53:46  OK http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack8-host13/1489679-repair/
    2017-12-16 17:51:59  -- http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/hosts/chromeos2-row8-rack8-host13/1489672-reset/
    2017-12-16 17:50:03  -- http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/163035372-chromeos-test/

The sequence above shows these events:
17:50:03  Test abort (symptom is an unexpected disconnect on the DUT).
17:51:59  Reset checks the DUT, and cannot restart chrome.
17:53:46  Repair also is unable to start chrome, and so re-installs
          a clean OS.
19:19:15  The clean OS works fine, and the DUT goes back to testing

Here are the relevant log bits from the reset task:
12/16 17:52:07.442 DEBUG|          ssh_host:0301| Running (ssh) 'stop ui; start ui' from 'reset|cleanup|cleanup_services|_restart_ui|run|run_very_slowly'
12/16 17:52:09.525 DEBUG|             utils:0280| [stdout] ui stop/waiting
12/16 17:52:09.870 DEBUG|             utils:0280| [stdout] ui start/running, process 3621
12/16 17:52:09.881 DEBUG|          ssh_host:0301| Running (ssh) 'bootstat_get_last login-prompt-visible' from 'wait_for_chrome_ready|poll_for_condition|<lambda>|get_chrome_session_ident|run|run_very_slowly'
[ ... ]
12/16 17:53:39.038 DEBUG|          ssh_host:0301| Running (ssh) 'bootstat_get_last login-prompt-visible' from 'wait_for_chrome_ready|poll_for_condition|<lambda>|get_chrome_session_ident|run|run_very_slowly'
12/16 17:53:39.489 ERROR|             utils:2739| Will raise error TimeoutError('Timed out waiting for login prompt',) due to unexpected return: False

The repair task collected a large number of chrome crash files; they
can be downloaded here:
    https://storage.cloud.google.com/chromeos-autotest-results/hosts/chromeos2-row8-rack8-host13/1489679-repair/20171612175343/crashinfo.chromeos2-row8-rack8-host13.tgz?_ga=2.245126661.-1892908568.1497571062

Initial triage starts with those crash files; passing to the gardener
for to look at them.