Look for ERROR too. Not sure if BAD actually ever shows up.

src/scripts/run_remote_tests.sh

 #!/bin/bash
 
 # Copyright (c) 2009 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Script to run client or server tests on a live remote image.
 
 # Load common constants.  This should be the first executable line.
 # The path to common.sh should be relative to your script's location.
@@ skipping 46 matching lines @@
 }
 
 # Returns an error if the test_result_file has text which indicates
 # the test was not run successfully.
 # Arguments:
 #   $1 - file name of autotest status for to check for success
 # Returns:
 #   None
 function is_successful_test() {
   local file="$1"
-  # To be successful, must not have FAIL or BAD in the file.
-  if egrep -q "(BAD|FAIL)" "${file}"; then
+  # To be successful, must not have BAD, ERROR or FAIL in the file.
+  if egrep -q "(BAD|ERROR|FAIL)" "${file}"; then
     return 1
   fi
   # To be successful, must have GOOD in the file.
   if ! grep -q GOOD "${file}"; then
     return 1
   fi
   return 0
 }
 
 # Removes single quotes around parameter
@@ skipping 166 matching lines @@
       fi
     else
       echo_color "red" ">>> FAILED: ${control_file}"
       cat "${test_status}"
     fi
     local end_time=$(date '+%s')
   done
 }
 
 main $@