Don't kick off an abort just because of a failed HWTest.
Don't kick off an abort just because of a failed HWTest.

When compile failures occur, it's often early in the build process, so
it's a good idea to abort any hardware test processes that might be
running. On the other hand, once we've finally got to the hardware test
phase, HWTest finishes and fails, it doesn't make sense to abort the
other HWTests.

BUG=chromium:271874
TEST=Run an example run with failing HWTests and confirm no abort runs.

Change-Id: I66cc8df2c5bc55aeb2e00a93a18ef6d999d0d197
Reviewed-on: https://gerrit.chromium.org/gerrit/66021
Reviewed-by: Chris Sosa <959d3d631fb6f17f1b07f751372041a1edb210d1@chromium.org>
Commit-Queue: David James <f231dc574bbeb62604660cbc162d1b8642a0a3af@chromium.org>
Tested-by: David James <f231dc574bbeb62604660cbc162d1b8642a0a3af@chromium.org>

bpsinc-native/src_third_party_chromite,bpsinc-native/src_third_party_chromite,chadversary/chromiumos.chromite,bpsinc-native/src_third_party_chromite,chadversary/chromiumos.chromite