Remove flaky annotations from testLaunchSingleTaskActivity.
- There are two reason to use waitForActivityRemoved to
replace waitForActivityState,
1. The SECOND_STANDARD_ACTIVITY can be removed from task after
SINGLE_TASK_ACTIVITY idled, thus it won't match the DESTROYED
condition because the activity could already gone. If so we
don't need to wait more 5 seconds for the activity state.
2. If the state of SECOND_STANDARD_ACTIVITY is exactly match
DESTROYED, this also means that this activity is not removed
from task, thus the test would fail at last assert.
Bug: 127741025
Test: atest ActivityStarterTests
Change-Id: Ibe31a95bedbb424cc494bd561a07f9c73c9d1e40
1 file changed