DO NOT MERGE: Protect against system checkers RuntimeException

a system checker runtime exception would kill the
invocation, changing this to only consider the
system checker failed.

If the root cause of the RuntimeException was a device
issue, a DNAE would eventually be triggered and properly
clean up the invocation.

Test: unit tests
run cts, manually fail a checker
Bug: 111752857

Change-Id: I3e2f5772b92e62a9dac377c47a8aab4eaed479e2
(cherry picked from commit 528eaf7d6c996309cdf558b9b6f698ad572d5bd5)
2 files changed
tree: 1b8594485c14afb0278fa3212c5b23e0324a83a7
  1. atest/
  2. prod-tests/
  3. proto/
  4. python-lib/
  5. remote/
  6. res/
  7. src/
  8. tests/
  9. util-apps/
  10. .classpath
  11. .gitignore
  12. .project
  13. Android.bp
  14. Android.mk
  15. atest_tradefed.sh
  16. CleanSpec.mk
  17. error_prone_rules.mk
  18. MANIFEST.mf
  19. OWNERS
  20. PREUPLOAD.cfg
  21. pylintrc
  22. README.md
  23. run_tf_cmd.sh
  24. script_help.sh
  25. TEST_MAPPING
  26. tradefed.sh
  27. tradefed_win.bat
  28. verify.sh
README.md

Trade Federation (TF / tradefed)

TF is a test harness used to drive Android automated testing. It runs on test hosts and monitors the connected devices, handling test scheduling & execution and device management.

Other test harnesses like Compatibility Test Suite (CTS) and Vendor Test Suite (VTS) use TF as a basis and extend it for their particular needs.

Building TF:

  • source build/envsetup.sh
  • tapas tradefed-all
  • make -j8

More information at: https://source.android.com/devices/tech/test_infra/tradefed/