zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2183) Concurrent Testing Processes and Port Assignments
Date Mon, 18 May 2015 17:55:01 GMT

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

Rakesh R commented on ZOOKEEPER-2183:

Ok, its pretty clear now. Thanks [~cnauroth] for the detailed explanation:) 

> Concurrent Testing Processes and Port Assignments
> -------------------------------------------------
>                 Key: ZOOKEEPER-2183
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2183
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: tests
>    Affects Versions: 3.5.0
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>             Fix For: 3.5.1, 3.6.0
>         Attachments: ZOOKEEPER-2183.001.patch, ZOOKEEPER-2183.002.patch, ZOOKEEPER-2183.003.patch,
ZOOKEEPER-2183.004.patch, ZOOKEEPER-2183.005.patch, threads-change.patch
> Tests use {{PortAssignment#unique}} for assignment of the ports to bind during tests.
 Currently, this method works by using a monotonically increasing counter from a static starting
point.  Generally, this is sufficient to achieve uniqueness within a single JVM process, but
it does not achieve uniqueness across multiple processes on the same host.  This can cause
tests to get bind errors if there are multiple pre-commit jobs running concurrently on the
same Jenkins host.  This also prevents running tests in parallel to improve the speed of pre-commit

This message was sent by Atlassian JIRA

View raw message