The adb_logcat_* scripts are extract attached devices names with
pattern 'w+', but it only works for real devices. Emulated devices
have names in form of 'emulator-5554' and '-' sign is not matched
by 'w+' parrent. This causes to logcat output to be missed while
tests are running
R=frankf@chromium.org, craigdh@chromium.org
TEST=Run tests with only emulators attached, ensure that resulting
log contains logcal output
Review URL: https://codereview.chromium.org/661843003
Cr-Original-Commit-Position: refs/heads/master@{#300242}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 044549b9d574c6fb633287a8ddb5f2df12be2b24
This way, we can invoke adb_logcat_monitor.py directly from
recipes. We cannot spawn a process which runs
adb_logcat_monitor.py (like we have been via
buildbot/bb_device_steps.py) from recipes as we cannot import
subprocess et al. from recipes.
BUG=286509
Review URL: https://codereview.chromium.org/24456002
git-svn-id: http://src.chromium.org/svn/trunk/src/build@226151 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
- Top-level scripts are kept under build/android.
- Utility libraries have been moved to build/android/pylib.
- Fixes all imports and headers.
This is in preparation for landing the "instrumentation" (java-based) tests,
which will reuse several of these components.
BUG=
TEST=existing android tests
Review URL: https://chromiumcodereview.appspot.com/10693110
git-svn-id: http://src.chromium.org/svn/trunk/src/build@145653 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
jbudorick
ripp
jbudorick@chromium.org
sivachandra@chromium.org
frankf@chromium.org
bulach@chromium.org
ilevy@chromium.org
creis@chromium.org