[
https://issues.apache.org/jira/browse/KAFKA-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ewen Cheslack-Postava updated KAFKA-2613:
-----------------------------------------
Assignee: Ewen Cheslack-Postava
Reviewer: Gwen Shapira
Status: Patch Available (was: Open)
Not sure whether this patch should actually close this issue, but it at least
makes the maxParallelForks configurable so we could set that flag on the
Jenkins builds.
> 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)
