Fixing flakiness of TestDetectUnresolvedProxy.

Fixing flakiness of TestDetectUnresolvedProxy.

If the AutoDetectProxy timed out resolving one address, it was
attempting to use the same resolver to resolve the next address,
which would always result in an assertion. This happened recently
a couple times on the Windows DrMemory bot because of its slowness.

TBR=pthatcher@webrtc.org

Committed: https://crrev.com/54433e72aabb2b01aa1c5c7b6a2ba91c2c01b348
Cr-Commit-Position: refs/heads/master@{#13326}

[Taylor Brandstetter, 2016-06-28 22:29:29]

deadbeef@webrtc.org changed reviewers:
+ pthatcher@webrtc.org, zhihuang@webrtc.org

[Taylor Brandstetter, 2016-06-29 17:10:23]

Description was changed from

==========
Fixing flakiness of TestDetectUnresolvedProxy.

If the AutoDetectProxy timed out resolving one address, it was
attempting to use the same resolver to resolve the next address,
which would always result in an assertion. This happened recently
a couple times on the Windows DrMemory bot because of its slowness.
==========

to

==========
Fixing flakiness of TestDetectUnresolvedProxy.

If the AutoDetectProxy timed out resolving one address, it was
attempting to use the same resolver to resolve the next address,
which would always result in an assertion. This happened recently
a couple times on the Windows DrMemory bot because of its slowness.

TBR=pthatcher@webrtc.org
==========

[Taylor Brandstetter, 2016-06-29 17:10:44]

Description was changed from

==========
Fixing flakiness of TestDetectUnresolvedProxy.

If the AutoDetectProxy timed out resolving one address, it was
attempting to use the same resolver to resolve the next address,
which would always result in an assertion. This happened recently
a couple times on the Windows DrMemory bot because of its slowness.

TBR=pthatcher@webrtc.org
==========

to

==========
Fixing flakiness of TestDetectUnresolvedProxy.

If the AutoDetectProxy timed out resolving one address, it was
attempting to use the same resolver to resolve the next address,
which would always result in an assertion. This happened recently
a couple times on the Windows DrMemory bot because of its slowness.

TBR=pthatcher@webrtc.org

Committed:
https://chromium.googlesource.com/external/webrtc/+/54433e72aabb2b01aa1c5c7b6...
==========

[commit-bot: I haz the power, 2016-06-29 17:10:45]

Description was changed from

==========
Fixing flakiness of TestDetectUnresolvedProxy.

If the AutoDetectProxy timed out resolving one address, it was
attempting to use the same resolver to resolve the next address,
which would always result in an assertion. This happened recently
a couple times on the Windows DrMemory bot because of its slowness.

TBR=pthatcher@webrtc.org

Committed:
https://chromium.googlesource.com/external/webrtc/+/54433e72aabb2b01aa1c5c7b6...
==========

to

==========
Fixing flakiness of TestDetectUnresolvedProxy.

If the AutoDetectProxy timed out resolving one address, it was
attempting to use the same resolver to resolve the next address,
which would always result in an assertion. This happened recently
a couple times on the Windows DrMemory bot because of its slowness.

TBR=pthatcher@webrtc.org

Committed: https://crrev.com/54433e72aabb2b01aa1c5c7b6a2ba91c2c01b348
Cr-Commit-Position: refs/heads/master@{#13326}
==========

[Taylor Brandstetter, 2016-06-29 17:10:46]

Committed patchset #1 (id:1) manually as
54433e72aabb2b01aa1c5c7b6a2ba91c2c01b348 (presubmit successful).

[commit-bot: I haz the power, 2016-06-29 17:10:46]

Patchset 1 (id:??) landed as
https://crrev.com/54433e72aabb2b01aa1c5c7b6a2ba91c2c01b348
Cr-Commit-Position: refs/heads/master@{#13326}

[Zhi Huang, 2016-06-29 17:16:22]

On 2016/06/28 22:29:30, Taylor Brandstetter wrote:

Sorry for the late reply as I'm not very familiar with the code in this area.
But the CL looks goods.  LGTM.