kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-2613) Consider capping `maxParallelForks` for Jenkins builds
Date Tue, 13 Oct 2015 01:27:06 GMT

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

ASF GitHub Bot commented on KAFKA-2613:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/kafka/pull/293


> Consider capping `maxParallelForks` for Jenkins builds
> ------------------------------------------------------
>
>                 Key: KAFKA-2613
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2613
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Ismael Juma
>            Assignee: Ewen Cheslack-Postava
>
> We currently set `maxParallelForks` to the number returned by `Runtime.availableProcessors`.
> {code}
>   tasks.withType(Test) {
>     maxParallelForks = Runtime.runtime.availableProcessors()
>   }
> {code}
> This returns the number of logical cores (including hyperthreaded cores) in the machine.
> This is usually OK when running the tests locally, but the Apache Jenkins slaves run
2 to 3 jobs simultaneously causing a higher number of timing related failures.
> A potential solution is to allow `maxParallelForks` to be set via a Gradle property and
use that property to set it to an appropriate value when the build is run from Jenkins.



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

Mime
View raw message