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 'correct' resolving for test hostname
Date Fri, 06 Feb 2015 02:42:35 GMT

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

Kai Zheng commented on HADOOP-11535:

Thanks Steve for the pointing. I checked it out and see the following domain names are reserved.

So according to this, we should check the tests and replace the domain names with the reserved
ones, to make sure they won't resolve. Will provide a patch accordingly.

> TableMapping related tests failed due to 'correct' resolving for 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
> 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 ( 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

View raw message