602996fe2559e1bcc4e8a32cd21a738950706ca7
Although commit2a84d1cbcffixed some flakyness issues in testNetworkCallbackMaximum so that it became stable when ran on its own, it introduced a new source of random failures because instead of registering callbacks after callbacks until a limit was reached, commit2a84d1cbcfchanged the test logic to push the assertions right up to the theoretical limit. More precisely when registering and unregistering PendingIntents in a loop, not introducing some delay for checking that previous PendingIntents have been effectively unregistered can cause the test to fail. This patch fixes this issue. Bug: 32561414 Bug: 62918393 Test: runtest frameworks-net testNetworkCallbackMaximum now succeeds 100 in a row on sailfish Change-Id: I086817a738ab99fd53ba76ca8faada6151f46472
Description
android_packages_modules_Connectivity
Languages
Java
81.4%
Kotlin
7.7%
AIDL
4.5%
C++
4.5%
C
1.7%
Other
0.1%