vadimt 2f41808e9b Updating logcat reading logic
Start a thread to read logcat synchronusly instead
of back-tracking at the end of the test

Also:
* Reusing the same logcat process for all checks. This eliminates
reading the log from its start for every gesture. We don’t kill that
process at the end, and don’t stop the thread. I’ve verified that
“am instrument” doesn’t hang, and the logcat process gets automatically
killed after the test process exits.
* Not using mStarted latch, as there is no need to wait until the reader
reaches the start mark.

Bug: 149422395
Change-Id: Ide4ed19ad8d099c41918f38c2b073b8b2e143b69
2020-02-20 22:02:52 +00:00
2020-02-06 14:16:34 -08:00
2020-02-06 14:16:34 -08:00
2020-02-17 12:38:58 -08:00
2020-02-20 22:02:52 +00:00
2019-05-17 23:19:58 -07:00
2020-01-17 11:24:43 -08:00
2019-12-05 11:18:52 +00:00
2019-11-05 16:49:58 -08:00
2020-01-17 11:24:43 -08:00
S
Description
No description provided
658 MiB
Languages
Java 57.2%
Kotlin 42.4%
AIDL 0.3%