[
https://issues.apache.org/jira/browse/SQOOP-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696060#comment-16696060
]
Hudson commented on SQOOP-3408:
-------------------------------
FAILURE: Integrated in Jenkins build Sqoop-hadoop200 #1232 (See
[https://builds.apache.org/job/Sqoop-hadoop200/1232/])
SQOOP-3408 Introduce a Gradle build parameter to set the default (fero:
[https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=74252163f0455747ed2a99eb6c2c9d0e48f3dedc])
* (edit) COMPILING.txt
* (edit) build.gradle
> Introduce a Gradle build parameter to set the default forkEvery value for the
> tests
> -----------------------------------------------------------------------------------
>
> Key: SQOOP-3408
> URL: https://issues.apache.org/jira/browse/SQOOP-3408
> Project: Sqoop
> Issue Type: Test
> Affects Versions: 1.4.7
> Reporter: Szabolcs Vasas
> Assignee: Szabolcs Vasas
> Priority: Major
> Attachments: SQOOP-3408.patch
>
>
> The [forkEvery
> parameter|https://docs.gradle.org/current/dsl/org.gradle.api.tasks.testing.Test.html#org.gradle.api.tasks.testing.Test:forkEvery]
> of the Gradle test tasks is currently set to 0 which means that all of the
> tests run in a single JVM (the only exception is the kerberizedTest task
> which requires a new JVM for every test class).
> The benefit of this setup is that the test tasks finish much faster since the
> JVM creation is a slow operation. However the Sqoop test framework seems to
> consume/leak too much memory which can lead to an OutOfMemoryError during the
> build if there is not enough memory on the machine running the tests.
> The goal of this JIRA is to introduce a new parameter to the Gradle build
> which can be used to set the default forkEvery parameter and thus prevent the
> JVM running out of memory.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
