You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2016/11/01 16:09:59 UTC

[jira] [Closed] (TINKERPOP-1537) Python tests should not use hard-coded number of workers

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

Daniel Kuppitz closed TINKERPOP-1537.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.2.4

CTR'ed via https://github.com/apache/tinkerpop/commit/333f2ab677bfb3e2ec35f1fb0123ec30eec248e3.

> Python tests should not use hard-coded number of workers
> --------------------------------------------------------
>
>                 Key: TINKERPOP-1537
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1537
>             Project: TinkerPop
>          Issue Type: Bug
>    Affects Versions: 3.2.3
>            Reporter: Daniel Kuppitz
>            Assignee: Daniel Kuppitz
>             Fix For: 3.2.4
>
>
> https://github.com/apache/tinkerpop/blob/tp32/gremlin-python/src/main/jython/tests/driver/test_driver_remote_connection.py#L88
> This test will fail on systems with less than 4 CPUs. Instead we should use something like {{min(4, multiprocessing.cpu_count())}}.
> Also see: http://stackoverflow.com/questions/1006289/how-to-find-out-the-number-of-cpus-using-python



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