reef-uni-release:186 failed

Builders failed on: 
- reef-uni-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/reef-uni-release/186


08/23 07:22:01.896 DEBUG|          ssh_host:0296| Running (ssh) 'cat /mnt/stateful_partition/unencrypted/preserve/powerwash_count' from '_call_run_once|run_once|_powerwash_count|run|wrapper|run_very_slowly'
08/23 07:22:54.384 DEBUG|             utils:0280| [stderr] Read from socket failed: Connection reset by peer
08/23 07:22:54.392 DEBUG|platform_Powerwash:0080| Powerwash count is: ''
08/23 07:22:54.393 DEBUG|              test:0389| Test failed due to Powerwash count didn't increase after powerwash cycle.. Exception log follows the after_iteration_hooks.
08/23 07:22:54.394 DEBUG|              test:0392| starting after_iteration_hooks
08/23 07:22:54.394 DEBUG|              test:0395| after_iteration_hooks completed
08/23 07:22:54.395 WARNI|              test:0612| The test failed with the following exception
Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/test.py", line 606, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 806, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 470, in execute
    dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 380, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/server/site_tests/platform_Powerwash/platform_Powerwash.py", line 61, in run_once
    raise error.TestFail("Powerwash count didn't increase after "
TestFail: Powerwash count didn't increase after powerwash cycle.



Looks like possibly a network flake (see "Read from socket failed: Connection reset by peer") of some kind. But the test is also pretty poor in handling this, as it ignores the SSH exit status. At a minimum, we could fix this to report the right error.

I'm not sure if this is a device issue we should look into also.