tree c1ff6a843574e5f65836e8f1a6e95e54cf2fbab7
parent 96ae6c0318b87f07f6c6753f346f6887f48d4b20
author Xiao Ma <xiaom@google.com> 1681461188 +0900
committer Xiao Ma <xiaom@google.com> 1681462177 +0900

Fix the flakyness: Argument(s) are different in integration test.

It's expected to receive bunches of onLinkPropertiesChange callbacks
during dual-stack provisioning until we see both IPv4 and IPv6 addresses
show up in the LinkProperties as well as other provisioning information.
However, sometimes we only see onLinkPropertiesChange callback once
during the provisioning, it only contains the IPv6 link-local address
and route and then both IPv4 and IPv6 provisioning succeed almost at the
same time, which results in another onProvisioningSuccess callback is
thrown rather than onLinkPropertiesChange callback, that's what we want
to capture in the test.

To avoid this flaky test, always wait IPv4 provisioning to complete with
success and then start IPv6 provisioning, this way guarantees
onLinkPropertiesChange callback is triggered whenever the LinkProperties
has update.

Bug: 277548168
Test: atest NetworkStackIntegrationTests --rerun-until-failure
Change-Id: I1cac4a184684004f1aed3988975b1d2e80496917