diff options
| author | Mark Salyzyn <salyzyn@google.com> | 2020-02-04 07:16:53 -0800 |
|---|---|---|
| committer | Mark Salyzyn <salyzyn@google.com> | 2020-02-04 09:01:31 -0800 |
| commit | 5dae6639a375b8e469a0b03905c8c49d4e2212de (patch) | |
| tree | ef8c5fdb494080be56df2acecc2c1bfc68b93378 /code_coverage/Android.bp | |
| parent | f39bfd1d47eef730124f5df72488ffe4dc458af6 (diff) | |
tests: handle legacy and new bootstat complete
Regression from commit cb1a8e7fdd231a9d1e95b1493ad716b9008dd81f
("Don't retrigger bootstat during userspace reboot.")
sys.boot_completed and either sys.logbootcomplete (legacy) or
sys.bootstat.first_boot_completed set to determine if the display
has gone active for bootstat. For adb remount test we have no
desire or need to wait for bootstat complete, reduce script
complexity.
Also solve a possible problem with no content supplied to xargs.
Signed-off-by: Mark Salyzyn <salyzyn@google.com>
Test: adb-remount-test.sh
Bug: 148804390
Bug: 135984674
Change-Id: Ieefddf583ff7422e8811d2e338a0f16c8943b0d7
Diffstat (limited to 'code_coverage/Android.bp')
0 files changed, 0 insertions, 0 deletions