diff options
| author | Kweku Adams <kwekua@google.com> | 2021-02-03 17:00:44 -0800 |
|---|---|---|
| committer | Kweku Adams <kwekua@google.com> | 2021-02-03 17:30:28 -0800 |
| commit | 970089c5da438e404319c0a937d7d526d3456dde (patch) | |
| tree | bad2b52ab7ec7721a1359502687f66b6bce5ffe5 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 9e86c288246049e840937fbd40d451529f9d8cda (diff) | |
Close preemption loop.
Prior to this change, whenever we preempted a job, the preempted job
would be stopped, but then we wouldn't explicitly start the higher
priority job until we re-evaluated all jobs and regenerated the pending
job list. This was inefficient. Now, whenever a job finishes (via
preemption or any other ending), JobConcurrencyManager will immediately
give the JobServiceContext a new job to start, if limits allow.
Bug: 178119369
Test: atest CtsJobSchedulerTestCases
Test: atest FrameworksMockingServicesTests:JobSchedulerServiceTest
Test: atest FrameworksServicesTests:PrioritySchedulingTest
Test: atest FrameworksServicesTests:WorkCountTrackerTest
Test: atest FrameworksServicesTests:WorkTypeConfigTest
Change-Id: I00a1aca6a3ec42cf6b62712313fa4d1698e34f51
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions