Thanks!

I guess that this occurs if the host is configured with a search
domain and that domain has a wildcard entry. That is not the most
common situation, but we may have users working in this kind of
environment. Therefore I will modify the tests so that they are
skipped dynamically if they are executed on a host that doesn't meet
the expectations.

Andreas

On Wed, Dec 22, 2010 at 00:30, sebb <seb...@gmail.com> wrote:
> On 21 December 2010 22:56, Andreas Veithen <andreas.veit...@gmail.com> wrote:
>> On Tue, Dec 21, 2010 at 23:40, sebb <seb...@gmail.com> wrote:
>>> On 21 December 2010 21:48, Gav... <ga...@16degrees.com.au> wrote:
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
>>>>> Sent: Wednesday, 22 December 2010 6:39 AM
>>>>> To: builds@apache.org
>>>>> Subject: [Hudson] Strange DNS behavior on ubuntu1
>>>>>
>>>>> All,
>>>>>
>>>>> Does anybody know why this.is.not.a.valid.hostname.at.all.no.way
>>>
>>> That host name is not guaranteed to always be invalid.
>>>
>>> If you want to reference an invalid hostname, then use the TLD
>>> .invalid, which is specially designed for this purpose.
>>>
>>> For example:
>>>
>>> myhost.invalid
>>>
>>> anotherhost.invalid
>>>
>>> AIUI all DNS resolvers should fail to resolve such host names.
>>
>> Yes, that was actually the next thing on my list to try. If you have
>> shell access, can you do a quick check if that indeed gives the
>> expected result?
>
> You can create your own task to do this.
>
> See for example one I just created:
>
> https://hudson.apache.org/hudson/job/Ubuntu1/2/console
>
> which unfortunately shows that Yahoo! DNS is (incorrectly) resolving
> the .invalid TLD
>
> Maybe someone should tell them...
>
> Ubuntu2 seems to be OK however:
>
> https://hudson.apache.org/hudson/job/Ubuntu2/2/console
>
>>>>> resolves to 98.137.132.14 (nx1.ycpi.vip.sp2.yahoo.net) on ubuntu1? We
>>>>> (Axis2) have a couple of test cases that use this host name with an
>>>>> assertion on the expected exception (UnknownHostException), but they
>>>>> now all fail because they get the wrong exception (ConnectException
>>>>> with connection timed out).
>>>>
>>>> Someone from Yahoo! - where Ubuntu1 is hosted - will have to answer that.
>>>>
>>>> Gav...
>>>>
>>>>>
>>>>> Andreas
>>>>
>>>>
>>>>
>>>
>>
>

Reply via email to