For TestResolverShutdown, use address that can't be resolved.

For TestResolverShutdown, use address that can't be resolved.

This test only currently works because stun.l.google.com has an IPv4
address and the TURN port is created with an IPv6 address. But the test
would start failing if/when it starts providing an IPv6 address. Which
may already be happening, as indicated by a recent test failure.

Committed: https://crrev.com/71cfe690b709d47432e0bcd12add737e2ed94fe6
Cr-Commit-Position: refs/heads/master@{#9841}

[Taylor Brandstetter, 2015-08-13 23:25:49]

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

[Taylor Brandstetter, 2015-08-13 23:25:49]

Hi Peter; one more small thing to review. I'm hoping it will fix this failure:
http://build.chromium.org/p/client.webrtc/builders/Linux%20Tsan%20v2/builds/3453

[pthatcher1, 2015-09-02 00:46:48]

lgtm

[Taylor Brandstetter, 2015-09-02 01:19:32]

The CQ bit was checked by deadbeef@webrtc.org

[commit-bot: I haz the power, 2015-09-02 01:19:45]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1290233003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1290233003/1

[commit-bot: I haz the power, 2015-09-02 02:01:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-02 02:01:52]

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