diff options
author | Tom Cherry <tomcherry@google.com> | 2017-02-22 17:38:00 -0800 |
---|---|---|
committer | Tom Cherry <tomcherry@google.com> | 2017-02-23 10:58:05 -0800 |
commit | 1fb04ff4e5d401d8a8caca2b4cd34706a883b536 (patch) | |
tree | 8d61b3bed0c148e45942319427117e32de2beae8 /libunwindstack/tests/MemoryFileTest.cpp | |
parent | 4bd3facbb1e79055f92e2ea8d42cb81552ffc6bb (diff) |
Make Condition use CLOCK_MONOTONIC
Changes to the REALTIME clock can cause Condition::waitRelative() to
timeout early or delayed. This behavior is undesired and new since
https://android-review.googlesource.com/#/c/181058/ moved the
underlying pthread_cond_timedwait() implementation to use absolute
timeouts rather than relative ones. Having Condition use
CLOCK_MONOTONIC prevents these timeout issues.
Bug: 34592766
Bug: 35678943
Test: Boot bullhead
Test: Ensure time changes do not cause Condition::waitRelative() to
timeout early or delayed
Change-Id: I3a8d7a48f9b42fe990c3c7331313b6d85aa546f9
Diffstat (limited to 'libunwindstack/tests/MemoryFileTest.cpp')
0 files changed, 0 insertions, 0 deletions