You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2015/10/07 13:58:26 UTC
[jira] [Resolved] (REEF-807) Set JVM max memory limit used in
testsuites properly
[ https://issues.apache.org/jira/browse/REEF-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dongjoon Hyun resolved REEF-807.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.14
Resolved in #540[https://github.com/apache/incubator-reef/pull/540]
> Set JVM max memory limit used in testsuites properly
> ----------------------------------------------------
>
> Key: REEF-807
> URL: https://issues.apache.org/jira/browse/REEF-807
> Project: REEF
> Issue Type: Bug
> Components: Maven
> Affects Versions: 0.12
> Reporter: Dongjoon Hyun
> Assignee: Dongjoon Hyun
> Priority: Trivial
> Fix For: 0.14
>
>
> After investigating JDK 1.7 Out-of-Memory build errors on Apache Jenkins Builds, I found that we does not set Surefire plugin option properly. As a result, Surefire JVM has used default JVM options, 1GB, and fails during GC. After setting properly, the build passed.
> I did the above experiments on an Ubuntu VM with 4GB RAM and OpenJDK 1.7. After resolving this issue, we can recover JDK 1.7 on our Apache Jenkins build again. It's a valuable for us to ensure JDK compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)