incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hunter Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BLUR-222) Random ports for unit tests
Date Mon, 16 Sep 2013 19:22:52 GMT

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

Hunter Williams commented on BLUR-222:
--------------------------------------

[~amccurry] I could make MiniCluster have a variable port. Although, I'm not sure that's what
you want. It would be by default a value unless you change it, which would also change the
zkconnectionstring. 

[~gbarton] Thanks. Not sure how to use this without possibly run into issues changing current
structure as I'm not familiar enough with the code.
                
> Random ports for unit tests
> ---------------------------
>
>                 Key: BLUR-222
>                 URL: https://issues.apache.org/jira/browse/BLUR-222
>             Project: Apache Blur
>          Issue Type: Bug
>          Components: Blur
>    Affects Versions: 0.2.0, 0.3.0
>            Reporter: Aaron McCurry
>
> There are a couple of unit tests that have hard coded ports, this is an issue on CI servers
that are multi-tenant.  The units should be random chosen when the tests run.
> The big 2 are ZooKeeperStatusClusterTest and BlurMiniCluster.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message