You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/31 00:55:53 UTC
[jira] [Updated] (HADOOP-11535) TableMapping related tests failed
due to 'successful' resolving of invalid test hostname
[ https://issues.apache.org/jira/browse/HADOOP-11535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HADOOP-11535:
--------------------------------------
Fix Version/s: 2.7.0
> 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
> Fix For: 2.7.0
>
> 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)