| commit | c0c3ac58e7083bdc69fad759a110429f72f42fb4 | [log] [tgz] |
|---|---|---|
| author | Guang Zhu <guangzhu@google.com> | Tue Apr 21 09:34:39 2020 -0700 |
| committer | Guang Zhu <guangzhu@google.com> | Tue Apr 21 09:44:43 2020 -0700 |
| tree | aadd7cbecb63d70da18d9e2ef50771487e1a28d4 | |
| parent | 85809fd0abdb0d186101066f01264d0b61935e84 [diff] |
improve the wait logic in nested ssh bugreport
If this is the first time running an adb command on remote VM,
the nested virtual device might not become visible to the adb
server immediately. This is due to the implementation of
adb_connector on remote VM.
This patch prefixed the bugreport command with a
`wait-for-device` to ensure that the device is visible first
or until the preset 15m timeout. The previous retry loop is
also removed now that the cause of the behavior is clear.
Bug: 154613608
Test: updated unit test
http://sponge/4503f5cc-0fc1-415e-9cb0-06e06317ae53
Change-Id: I2269be1085be23ecf0e97658502d387cbcc0d9f1
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:
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.