If we have an instance name always attempt to clean it

Even if acloud didn't report it as properly boot, if we
figure out an instance name from the logs, attempt to
clean them to at least properly set the gce_instance_cleaned
flag.

Test: unit tests
Bug: 159328635
Change-Id: I5cca5f3185180f36230c73add959f1bedf284c3f
2 files changed
tree: 9c640439e3dd8f4a6217f266490eb303b2537035
  1. atest/
  2. clearcut_client/
  3. common/
  4. common_util/
  5. device_build_interfaces/
  6. global_configuration/
  7. invocation_interfaces/
  8. isolation/
  9. lite/
  10. proto/
  11. python-lib/
  12. remote/
  13. res/
  14. src/
  15. test_framework/
  16. test_result_interfaces/
  17. tests/
  18. util-apps/
  19. .classpath
  20. .gitignore
  21. .project
  22. Android.bp
  23. Android.mk
  24. atest_tradefed.sh
  25. CleanSpec.mk
  26. error_prone_rules.mk
  27. MANIFEST.mf
  28. OWNERS
  29. PREUPLOAD.cfg
  30. pylintrc
  31. README.md
  32. run_tf_cmd.sh
  33. script_help.sh
  34. TEST_MAPPING
  35. tradefed.sh
  36. tradefed_win.bat
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/

See more details about Tradefed Architecture at: https://source.android.com/devices/tech/test_infra/tradefed/architecture

If you are a tests writer you should start looking in the test_framework/ component which contains everything needed to write a tests in Tradefed.