- tricky-chrome-pfq: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8923987891466622656

The most recent PFQ run failed because of this issue.

Seems there are issues with chromeos4-row2-rack4-host5 and chromeos4-row2-rack4-host5.

Tests lose connectivity to DUTs. Examples of following errors are seen in several tests:


*****:
01/18 08:47:47.778 INFO |        server_job:0217| 	FAIL	tast	tast	timestamp=1547830067	localtime=Jan 18 08:47:47	Failed to run tast (last line: 2019/01/18 08:47:29 Failed to run tests: EOF): Command <'/usr/local/tast/tast' -verbose=true -logtime=false list -build=false '-remotebundledir=/usr/local/tast/bundles/remote' '-remotedatadir=/usr/local/tast/data' '-remoterunner=/usr/local/tast/remote_test_runner' -json=true 'chromeos4-row2-rack4-host5:22' '(!disabled && !"group:*" && !informational && "dep:android")'> failed, rc=1, Command returned non-zero exit status
  * Command: 
      '/usr/local/tast/tast' -verbose=true -logtime=false list -build=false
      '-remotebundledir=/usr/local/tast/bundles/remote'
      '-remotedatadir=/usr/local/tast/data'
      '-remoterunner=/usr/local/tast/remote_test_runner' -json=true
      'chromeos4-row2-rack4-host5:22' '(!disabled && !"group:*" &&
      !informational && "dep:android")'
  Exit status: 1
  Duration: 0.167536973953
  
  stderr:
  2019/01/18 08:47:29 Connecting to chromeos4-row2-rack4-host5:22
  2019/01/18 08:47:29 Failed to run tests: EOF


*****:
01/18 08:52:31.214 ERROR|   logging_manager:0626| Lost SSH connection to chromeos4-row2-rack4-host4:22: EOF, Test did not finish


*****:
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
AutotestRunError: Aborting - unexpected final status message from client on chromeos4-row2-rack4-host5