Right, on the EC2 jenkins I had to increase the heap size of the slave host process itself, not our forked test JVMs.
On Mon, Apr 8, 2013 at 10:32 AM, Stack <st...@duboce.net> wrote: > On Mon, Apr 8, 2013 at 8:29 AM, Nicolas Liochon <nkey...@gmail.com> wrote: > > > I was under the impression that it was a hudson/jenkins stack, not a > maven > > one? > > > Pardon me. I reread the stack trace. Yeah, this is post-maven copying of > results so yeah a jenkins issue. What I found in the past is that some of > our test output is massive (I downloaded the test result to take a look) or > rather, can be massive on occasion; e.g. replication tests. IIRC, it was an > in-memory realization of some xml report that was bringing on the OOME.... > Workaround seemed to be fixing the test producing all the output. Which > test run was this? I can take a look since I looked in the past. > > Thanks N, > St.Ack > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
