Merge pull request #3139 from akoeplinger/dns-test
authormonojenkins <jo.shields+jenkins@xamarin.com>
Thu, 9 Jun 2016 13:35:12 +0000 (14:35 +0100)
committermonojenkins <jo.shields+jenkins@xamarin.com>
Thu, 9 Jun 2016 13:35:12 +0000 (14:35 +0100)
commit975fc2134131e0c2e6c689df0c7d2d4a4ce62b00
treedf9cfc30cb59c7fe9f5aa1abad873313d9219b9a
parent19880afc7a1bb3339e790897884fff473ba5914f
parentea4ad8118539b954ba43e4cca99f6443bd5b2e71
Merge pull request #3139 from akoeplinger/dns-test

[System] Make ServicePointTest.DnsRefreshTimeout test more reliable

We are still seeing quite rare failures of this test:

```
HostEntry should result in the same IPHostEntry object.
  Expected: same as <System.Net.IPHostEntry>
  But was:  <System.Net.IPHostEntry>

+++++++++++++++++++
STACK TRACE:
at MonoTests.System.Net.ServicePointTest.DnsRefreshTimeout () [0x00045] in /Users/builder/jenkins/workspace/test-mono-mainline/label/osx-i386/mcs/class/System/Test/System.Net/ServicePointTest.cs:228
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00038] in /Users/builder/jenkins/workspace/test-mono-mainline/label/osx-i386/mcs/class/corlib/System.Reflection/MonoMethod.cs:309
```

Since the test is only checking if expiring of the cached DNS lookup works, we don't really need to use an external domain name for this as "localhost" works just fine as well and typically doesn't trigger a DNS query which makes the test more reliable against network issues.

@monojenkins merge