RESTRICT AUTOMERGE Fix CTS failures in heavy weight app tests
With the fix regarding the visibility of trampoline activity, the proc state would be evaluated once more in between the foreground and the cached state. Since the proc state transition isn't well defined - typically only the initial and end state matters, it'll make sense to update the CTS test code here. Cherry pick from master, fix flaky tests in CtsAppTestCases. Bug: 139372994 Test: atest android.app.cts.ActivityManagerProcessStateTest Change-Id: Ie36b959b2101ef5fef1139c7d44396f9398d178d
Loading
Please sign in to comment