You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hongchao Deng (JIRA)" <ji...@apache.org> on 2015/05/14 18:51:01 UTC

[jira] [Commented] (ZOOKEEPER-2183) Concurrent Testing Processes and Port Assignments

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

Hongchao Deng commented on ZOOKEEPER-2183:
------------------------------------------

Made mistake on "CHANGES.txt" when switching branches...

Committed another fix to branch-3.5:
https://github.com/apache/zookeeper/commit/419756a3ff3be986d3bbcef12ebdfba5c1b68412

Feeling guilty for it. Will be careful on future commits.

> 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 runs.



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