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
