diff options
| author | 2024-05-22 17:57:29 +0200 | |
|---|---|---|
| committer | 2024-05-22 17:58:43 +0200 | |
| commit | e7c6dfafad534181f5382557000d26685f4d1e54 (patch) | |
| tree | 98c61fa252b28f5602662c552d7c7e3294195e28 /native/android/input.cpp | |
| parent | e80f8c060cc3df4fcd4593c89077833d0a61f328 (diff) | |
Fix KeyguardTransitionRepository tests
I previously changed the log level on this in ag/27069661 as I thought
that this is a possible scenario that we should warn about but several
scenarios are possible where I would not consider this a error/failure.
For example any component that might update a manual transition could
attempt to do so right after some other component started a new
transition with `startTransition()` above. This would invalidate the
UUID but in my opinion just ignoring the update is fine. We should warn
about it so potential bugs resulting from this can be noted but I would
expect the system to continue to behave fine.
However, this made KeyguardTransitionRepositoryTests fail that I was not
aware of because the entire class is marked as flaky.
We can solve this either by changing back to wtf or removing/adjusting
the tests.
Bug: 341261406
Test: TEST_ONLY
Flag: TEST_ONLY
Change-Id: I017aac3845df5e4b2557d8b36dfadffe723ecf5e
Diffstat (limited to 'native/android/input.cpp')
0 files changed, 0 insertions, 0 deletions