these tests fork some jvms so it can be that you really don't have enough space. Maybe follow it while the test is running
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-10-14 15:42 GMT+02:00 Daniel Kasmeroglu <[email protected]>: > Hi, > > I'm currently a little bit in a pickle. I'm trying to get the complete > build to run under my own CI environment (Jenkins) so I can make sure > that the tests are getting green again. > > Unfortunately I'm stuck at itests/failover which doesn't seem to work on > my CI. The weird thing is that I can run it on my dev system (Windows 7) > without any problem. Furthermore I've checked the Apache CI which shows > that this module works there as well so it's likely that my system is > the cause of failure. > > But for some weird reasons it's not working on my CI which is an Ubuntu > 12.04 LTS. I've tried the builds using oracle-jdk7 and open-jdk7 but > none of them seemed to work. The build fails as part of the complete > reactor build as well as a single module (meaning executed by myself on > my server). > > The error claims that the JVM for the StandaloneServer could not > allocate enough heap space (I've got at least 6GB free space available > which should be much more than sufficient). Of course I've checked that > I'm using 64-Bit JVMs and I've planted -Xmx all over the place but > nothing seems to work. > > As I'm out of ideas I'm hoping that someone could give me a hint ? > > > Best regards > > Daniel Kasmeroglu
