If a retry config is used that is not rescheduling allow it

To be compatible of older retry config and be able to run
them. Do not hard fail, simply print an error and use
their config.

Test: unit tests
Bug: None
Change-Id: I98b99a526e2cbb271bff26a7598953705b5f4f64
3 files changed
tree: 9b8c380cc0f75e988e4c45ed81c1f224902a9f4c
  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/