Skip to content

Commit

Permalink
Removes max heap size setting used for build
Browse files Browse the repository at this point in the history
Limiting the heap to 1G is suspect of causing excessive GC work which
 leads to failed tests, especially in large cluster HA ITs. Removing
 it seems to have no downsides so it is considered a good attempt at
 fixing the random test failures we see.
  • Loading branch information
digitalstain committed Jul 21, 2016
1 parent fcedeec commit a9094f5
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion pom.xml
Expand Up @@ -32,7 +32,7 @@
<bouncycastle.version>1.52</bouncycastle.version>
<generate-config-docs-phase>prepare-package</generate-config-docs-phase>
<hsqldb.version>2.3.2</hsqldb.version>
<test.runner.jvm.settings>-Xmx1G -XX:MaxPermSize=128M -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=target/test-data -Dorg.neo4j.unsafe.impl.internal.dragons.UnsafeUtil.DIRTY_MEMORY=true -XX:-OmitStackTraceInFastThrow</test.runner.jvm.settings>
<test.runner.jvm.settings>-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=target/test-data -Dorg.neo4j.unsafe.impl.internal.dragons.UnsafeUtil.DIRTY_MEMORY=true -XX:-OmitStackTraceInFastThrow</test.runner.jvm.settings>
<doclint-groups>reference</doclint-groups>
</properties>

Expand Down

0 comments on commit a9094f5

Please sign in to comment.