Am 02/20/17 um 01:10 schrieb Tibor Digana: > I meant this build which is in good conditions > https://builds.apache.org/view/Maven%20Master%20Release%20Status/job/maven-master-release-status-test-surefire-linux/30/console > > Can somebody explore what is different between these two surefire builds > (failed and successful) and why?: > https://builds.apache.org/view/Maven%20Master%20Release%20Status/ > https://builds.apache.org/job/maven-surefire/
Please see the attached patch. System.out and System.err do buffering internally in Java. System.exit seems to not flush/close those streams internally. I really think we just need to close System.in/System.err manually everywhere before exiting to get the buffers flushed correctly. Regards, -- Christian
diff --git a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java index b76df2f..7b9ec7d 100644 --- a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java +++ b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java @@ -243,6 +243,8 @@ private static void exit( int returnCode, Shutdown shutdownType, CommandReader r reader.stop(); } launchLastDitchDaemonShutdownThread( returnCode ); + System.out.close(); + System.err.close(); System.exit( returnCode ); case DEFAULT: // refers to shutdown=testset, but not used now, keeping reader open
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org