slachiewicz opened a new issue, #3624: URL: https://github.com/apache/maven-surefire/issues/3624
Affected version: master at d7c7e359e. `SurefireForkChannel` binds loopback with backlog 1 (maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/extensions/SurefireForkChannel.java:99-100), accepts exactly one client in `tryConnectToClient` (line 108), and verifies the session token with a blocking read that has no deadline (line 188). `ForkStarter` then awaits the fork process without a bound (line 657). A process that connects to the ephemeral port first and never sends the token consumes the only accept; the real fork cannot attach and the build waits indefinitely. There is no timeout on the pre-authentication read or on the accept. Expected behavior: bound the accept/verification window and fail the build with a clear diagnostic if the expected client does not authenticate in time. A loopback fixture can open one connection without the token and assert that the channel times out rather than hanging. -- 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]
