hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11535) TableMapping related tests failed due to 'successful' resolving of invalid test hostname
Date Sat, 07 Feb 2015 02:41:35 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14310482#comment-14310482
] 

Kai Zheng commented on HADOOP-11535:
------------------------------------

Thanks Steve for committing the patch.

> TableMapping related tests failed due to 'successful' resolving of invalid test hostname
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-11535
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11535
>             Project: Hadoop Common
>          Issue Type: Test
>            Reporter: Kai Zheng
>            Assignee: Kai Zheng
>            Priority: Minor
>         Attachments: HADOOP-11535-v1.patch
>
>
> When mvn test in my environment, it reported the following.
> {noformat}
> Failed tests: 
>   TestTableMapping.testClearingCachedMappings:144 expected:</[rack1]> but was:</[default-rack]>
>   TestTableMapping.testTableCaching:79 expected:</[rack1]> but was:</[default-rack]>
>   TestTableMapping.testResolve:56 expected:</[rack1]> but was:</[default-rack]>
> {noformat}
> It's caused by the good resolving for the 'bad test' hostname 'a.b.c' as follows.
> {noformat}
> [drankye@zkdesk hadoop-common-project]$ ping a.b.c
> PING a.b.c (220.250.64.228) 56(84) bytes of data.
> {noformat}
> I understand it may happen in just my local environment, and document this just in case
others also meet this. We may use even worse hostname than 'a.b.c' to avoid such situation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message