Tibor17 commented on pull request #355: URL: https://github.com/apache/maven-surefire/pull/355#issuecomment-874011834
@kriegaex I have the source code in my mind and I know what should be done with the config parameter `<forkedProcessTimeoutInSeconds>15</forkedProcessTimeoutInSeconds>`. You can see this in my commit. Do you know how it works? You have to trust me that I know better than you and I take the responsibility for zombie processes. I am aware that they may happen in the TCP is broken again and that the user has to use `forkedProcessTimeoutInSeconds` but it cannot be solved like this in this PR. We have some way to inform the users about the features in surefire and their possible issues and we can propose treatments. I can see the risk in the ITs and we know what should be done, but the problem with this PR looks like a bug after HEAD commit in master - that's the problem, and many other contributors use to write straightforward and brief definition of issue. We need to have time to think about a solution to keep backward compatibility with `forkedProcessTimeoutInSeconds` and provide a solution b ut the brain needs to have the time to think about it and this is normal. And normal is to post an issue in Jira to not to forget it. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
