Removing number of threads used in background execution
to prevent system thrashing Bug: 188541475 Test: Presubmit Change-Id: Iff73abeab813d1b80a1ff85b69723dce0bef8005
This commit is contained in:
1 parent
5bb515b6cc
commit
a76bc76317
3 files changed
+8
-20
No files matched your search
@@ -15,7 +15,7 @@
|
||||
*/
|
||||
package com.android.launcher3.model;
|
||||
|
||||
import static com.android.launcher3.util.Executors.createAndStartNewForegroundLooper;
|
||||
import static com.android.launcher3.util.Executors.createAndStartNewLooper;
|
||||
import static com.android.launcher3.util.LauncherModelHelper.TEST_PACKAGE;
|
||||
|
||||
import static org.junit.Assert.assertEquals;
|
||||
@@ -74,7 +74,7 @@ public class ModelMultiCallbacksTest {
|
||||
|
||||
// Since robolectric tests run on main thread, we run the loader-UI calls on a temp thread,
|
||||
// so that we can wait appropriately for the loader to complete.
|
||||
mTempMainExecutor = new LooperExecutor(createAndStartNewForegroundLooper("tempMain"));
|
||||
mTempMainExecutor = new LooperExecutor(createAndStartNewLooper("tempMain"));
|
||||
ShadowLooperExecutor sle = Shadow.extract(Executors.MAIN_EXECUTOR);
|
||||
sle.setHandler(mTempMainExecutor.getHandler());
|
||||
}
|
||||
|
||||
Reference in new issue
Block a user