diff options
| author | Louis Chang <louischang@google.com> | 2018-12-10 18:09:06 +0800 |
|---|---|---|
| committer | Louis Chang <louischang@google.com> | 2018-12-17 18:57:57 +0800 |
| commit | c3f29da921367cf7ef63008bc899edcb821a8f2b (patch) | |
| tree | 6ff275e73d7ea8bbdad49a51747ca951a9be3513 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 25e0861b277a890d4d2bcc763a9414e28af04fc5 (diff) | |
Do not report resized before sending new configuration
When display size changed, we reported to client that its windows
should be resized (but with old configuration). The new configuration
was then updated later. Since the IWindow#resized is a one way
binder call, there is no guarantee that client has completed
scheduling window-resized messages before the new configuration
updating request. So, test case was flaky while running on CF, which
had failed if the client updated to new configuration prior to handle
window resized.
Bug: 121105810
Test: atest ActivityManagerMultiDisplayTests
Change-Id: Ic661bc36494d268a2e712a079ba26baf47626130
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions