We have performance tests. This means your machine should run only this build. The GC may affect the success therefore my fine tuning is MAVEN_OPTC=-server -Xmx768m -XX:MaxMetaspaceSize=864m. Of course MaxMetaspaceSize is available in JDK8. Use MaxPemSize in JDK7 or JDK6. The ideal would be to have 4 Core CPU x64, SSD where the build takes only 45 minutes. $ mvn -P run-its install
On Mon, Mar 13, 2017 at 11:04 PM, Guillaume Boué <gb...@apache.org> wrote: > Hi, > > I finished setting up a FreeBSD VM with a couple of Maven and JDK > versions, so I'll be testing this extensively (on Ubuntu as well). Thanks > for the work! > > Guillaume > > > > Le 13/03/2017 à 10:46, Tibor Digana a écrit : > >> Hi All, >> >> The new branch SUREFIRE-1342 solves an issue when entire testset completed >> however the surefire's forked JVM finished printing serious issue. We >> know >> that the JVM did not crash however it looks so: >> >> The forked VM terminated without saying properly goodbye. VM crash or >> System.exit called ? >> >> >> The problem is solved in the branch and ready to be tested. >> >> The entire problem was concurrency issue where the forked JVM sent "bye" >> event to the Maven process via stdout but Maven process has not drained >> shared memory yet and Maven process was therefore slower to receive the >> event than the forked process which exited. Due to the "bye" event was not >> determined by Maven process in particular time, this error came up. >> We implemented ACK command which confirms such event has been received by >> Maven process. The shared memory is drained directly by Maven process. >> >> Cheers >> Tibor >> >> > > --- > L'absence de virus dans ce courrier électronique a été vérifiée par le > logiciel antivirus Avast. > https://www.avast.com/antivirus > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Cheers Tibor
