diff options
| author | Kweku Adams <kwekua@google.com> | 2021-03-29 17:03:54 -0700 |
|---|---|---|
| committer | Kweku Adams <kwekua@google.com> | 2021-03-30 10:23:40 -0700 |
| commit | 626ec2902cdd876f33a3e588053724ba0f45af6b (patch) | |
| tree | 1fab03084fce2fbb67adace349a552720f336863 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | ddf368aa33e5163e6e1651ca4cf982bd81bf6aee (diff) | |
Fix async behavior and address possible race conditions.
1. Don't release the lock until we've fully processed an app or user
removal so that JS stays in a consistent state outside of the lock.
Before, we released the lock between cancelling jobs and telling
controllers of the removal, so there was a short period where JS was
internally inconsistent and an app scheduling a job could land in JS's
inconsistency.
2. Actually lock around methods that require the lock be held.
Bug: 183921387
Test: atest frameworks/base/services/tests/servicestests/src/com/android/server/job
Test: atest frameworks/base/services/tests/mockingservicestests/src/com/android/server/job
Test: atest CtsJobSchedulerTestCases
Change-Id: I440e3c7753d119e025b0359d2b35bec90fa19628
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions