Allow remote shell session to be disabled when python process is interrupted

When test times out and python process is interrupted, the shell session via RPC connection becomes invalid.
If the framework proceed with shell commands in tearDown functions, it will stuck on receiving response from TCP server.

This CL adds a enable/disable switch to shell mirror. When test timeout is detected, the base_test runner automatically turns of the shell mirror, so all shell commands will be responsive.

Bug: 37579963
Test: vts-tradefed; run vts-codelab
Signed-off-by: Yuexi Ma <yuexima@google.com>
Change-Id: I6895e5bebb20d56c20a67d3172e09fa0180af8cb
(cherry picked from commit 1b3d43a5bd8d125dc3e5bf72f0109e3bcdc04b12)
4 files changed
tree: 0a97e3dfab0e59c07005ace4692f47be1a58033d
  1. agents/
  2. compilation_tools/
  3. doc/
  4. drivers/
  5. hals/
  6. harnesses/
  7. proto/
  8. runners/
  9. script/
  10. specification/
  11. testcases/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitignore
  16. __init__.py
  17. Android.bp
  18. OWNERS
  19. PREUPLOAD.cfg
  20. README.md
  21. setup.py
README.md

Android Vendor Test Suite (VTS)

VTS consists of a set of testing frameworks and test cases, designed to help enhance the robustness, reliability, and compliance of:

  • the Android system (e.g., Core HALs and libraries) and
  • low-level system software (e.g., kernel, module, and firmware).

VTS has mainly two types of test suites:

  • automated (e.g., record-and-replay and fuzzing) and
  • structural (e.g., gTest and host-driven python) testing.

While the VTS framework and test cases are designed for userdebug or eng build devices, some test cases can be run on user build devices using its app namely, VTS Agent App.

Table of Contents

  1. VTS User Manual
  2. Where to find VTS test cases
  3. VTS Test Developer Manual (Codelab)