tree 710f65c288c7b380212b62f73d31a31313feae77
parent a21f10ff5514a993a35c874caec2c5237f89effa
author Qasim Javed <qasimj@google.com> 1663259488 -0700
committer Qasim Javed <qasimj@google.com> 1663698420 -0700

Wait for a string to appear in logs.

Currently, we have to wait for arbitrary amount of time before we check
the log for a particular string. Instead of that, add functionality to
wait for a provided string to appear in the logs.

When an fd is dup?()'ed, the oldfd and the newfd share the offset.
So when the offset is changed on the oldfd using lseek, that change in
offset is applied to the newfd as well. In the context of this change,
it means that when we Rewind(), that also changes where the logs will be
written in the backing store. It can cause problems if we are
Rewind()'ing while logs are being written.

This change keeps the dup'ed fd since its needed to create a backing
store. However, it creates adds a new fd which uses the open system call
to get a new fd to the underlying backing store file. Since this is a
separate fd, an lseek on this fd will not result in a change in offset
on the newfd and oldfd provided to dup3 system call.

Bug: 246955322
Tag: #gd-refactor
Test: atest bluetooth_test_gd_unit

Change-Id: Ib2fcfeef82d3419f4c02e1815b907b0b6ac499a9