Hi, this may solve the immediate issue with the test failure, but it probably also hides an memory problem with our tests. in the past I tried to first identify and fix memory leaks and only then increase the heap if really necessary. do you know what is holding on to the memory?
Regards Marcel On 09/02/16 19:17, "Stefan Egli" wrote: >Hi, > >Looks like we need to give our travis run [0] more memory. OAK-3986 was >likely partly slowing down due to memory becoming low. Now it looks like >ConcurrentAddIT is failing [1] for the same reason too (can reproduce this >locally: default memory settings result in OOME). I'm guessing adding this >to the .travis.yml would do the trick? > >env: > >global: > >- JAVA_OPTS="-Xmx1G" > > >Cheers, >Stefan >-- >[0] - https://travis-ci.org/apache/jackrabbit-oak/builds >[1] - >Running org.apache.jackrabbit.oak.jcr.ConcurrentAddIT >No output has been received in the last 10 minutes, this potentially >indicates a stalled build or something wrong with the build itself. > >The build has been terminated > >
