[
https://issues.apache.org/jira/browse/HADOOP-7381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093001#comment-13093001
]
Hadoop QA commented on HADOOP-7381:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12482131/hadoop-7381.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/94//console
This message is automatically generated.
> FindBugs OutOfMemoryError
> -------------------------
>
> Key: HADOOP-7381
> URL: https://issues.apache.org/jira/browse/HADOOP-7381
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Affects Versions: 0.20.205.0
> Environment: FindBugs 1.3.9, ant 1.8.2, RHEL6, Jenkins 1.414 in
> Tomcat 7.0.14, Sun Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed
> mode)
> Reporter: Joep Rottinghuis
> Assignee: Joep Rottinghuis
> Priority: Minor
> Attachments: hadoop-7381.patch
>
>
> When running the findbugs target from Jenkins, I get an OutOfMemory error.
> The "effort" in FindBugs is set to Max which ends up using a lot of memory to
> go through all the classes. The jvmargs passed to FindBugs is hardcoded to
> 512 MB max.
> We can leave the default to 512M, as long as we pass this as an ant parameter
> which can be overwritten in individual cases through -D, or in the
> build.properties file (either basedir, or user's home directory).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
