[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #343: SUREFIRE-1881 Adds additional debug log and fork connection timeout

[GitBox <gi...@apache.org>]

Tibor17 edited a comment on pull request #343:
URL: https://github.com/apache/maven-surefire/pull/343#issuecomment-813987059


   @reinhapa 
   I commented the body of both tests and it worked.
   Then I made a second experiment and logarithmicaly uncommented the parts. I can say that Lines 96 - 99 cause a corrupted stream in process pipes.
   In this experiment I used the version 3.0.0-M5.
   It is most probable that M5 is more restrictive than M4.
   No I will explain to you how the communication works and what's going on. After the JVM has finished the tests and sends all events regarding the tests, the JVM is about to exit. The JVM exit is not so straight because the Surefire fork JVM sends the event `BYE` and the plugin JVM has to send `BYE_ACK`. The Surefire JVM did not receive `BYE_ACK` within 30 seconds and so the JVM killed itself.
   Can you analyse your code in the test and check what the JUnit Rule does with std/out?
   That's the reason why we want to use TCP.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org