Fix flaky test RepeatedSetup_NoRedundantPrivateDnsValidation
There is a time gap between the time when PrivateDnsConfiguration reports onPrivateDnsValidationEvent and the time when PrivateDnsConfiguration updates its map which is used for tracking validation threads. If the test starts a subsequent setup (which expects the resolver to begin a new validation) before PrivateDnsConfiguration updates the map, the expected validation won't start because PrivateDnsConfiguration thinks the previous validation hasn't finished. This change is a workaround which adds waiting time to avoid the timing issue, and the test running time increases 300ms. Bug: 150678049 Bug: 151990391 Test: resolv_integration_test passed Merged-In: I176d7d20b7edc79b37b954602961c149aef64348 Change-Id: I9d9a456dd3a030eea8efc8d761e295ee7a4f179d (cherry picked from commit 5fa66eac)
Loading
Please register or sign in to comment