diff options
| author | Charles Chen <charlesccchen@google.com> | 2022-04-15 23:33:25 +0800 |
|---|---|---|
| committer | Charles Chen <charlesccchen@google.com> | 2022-04-20 17:41:20 +0800 |
| commit | edf1b37a0821b3bc1b0384386ded3cd3bad81be9 (patch) | |
| tree | 73ae916a22e00fb190274695bba4056ca634b2ff /core/java/android/util/SparseSetArray.java | |
| parent | 99b30edb9ecd1c70086792928215f5d3a97666e2 (diff) | |
Fix testRegisterComponentCallbacksOnWindowContext flaky
This flakiness is due to race of config updates when WindowContext attaches to
DisplyArea.
This CL fixed it by:
1. Don't dispatch config updates to the client side when registering to
DA. We have reported the value by the return value of
#attachWindowContextToDisplayArea.
2. Use Handler#runWithScissors when attahing DA or DC. It can prevent
WindowContext reports stale config values and also guarantee the order of
onConfigurationChanged call.
Bug: 190019118
fixes: 228911504
Test: atest RegisterComponentCallbacksTest --iterations
Test: atest WindowContextTest WindowContextTests
Test: atest WindowMetricsWindowContextTests
Change-Id: I496d00bbfdc20b9bbf433d5d8ec65bf1f46d3dd3
Diffstat (limited to 'core/java/android/util/SparseSetArray.java')
0 files changed, 0 insertions, 0 deletions