You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Arshad Mohammad (JIRA)" <ji...@apache.org> on 2015/12/08 16:45:10 UTC

[jira] [Resolved] (ZOOKEEPER-2337) Fake "invalid" hostnames used in tests are sometimes valid

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arshad Mohammad resolved ZOOKEEPER-2337.
----------------------------------------
    Resolution: Duplicate

> Fake "invalid" hostnames used in tests are sometimes valid
> ----------------------------------------------------------
>
>                 Key: ZOOKEEPER-2337
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2337
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.4.7, 3.5.1, 3.6.0
>            Reporter: Timothy Ward
>            Assignee: Timothy Ward
>             Fix For: 3.4.8, 3.5.2, 3.6.0
>
>
> Some of the ZooKeeper tests use "fake" hostnames to trigger host resolution failures. The problem with this is that it uses valid hostnames which are sometimes configured in VMs.
> At the moment I am unable to build cleanly because I get test failures on the two test methods that do this. The tests work equally well if syntactically invalid hostnames are used, and the test cases become more portable at the same time.
> The affected test cases are:
> org.apache.zookeeper.test.StaticHostProviderTest.testTwoInvalidHostAddresses and org.apache.zookeeper.test.StaticHostProviderTest.testOneInvalidHostAddresses
> See GitHub pull request https://github.com/apache/zookeeper/pull/48 for a proposed fix



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