slachiewicz opened a new issue, #3616: URL: https://github.com/apache/maven-surefire/issues/3616
Affected version: master at d7c7e359e. `ForkClient.tryToTimeout` (maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java:314-329) requires `testSetStartedAt > START_TIME_ZERO`. The only writer of `testSetStartedAt` is `TestSetStartingListener.handle` (lines 142-147, 352-359), so before the fork reports its first test set the timeout clock is still zero. `ForkStarter.fork` calls `exec.awaitExit()` without a deadline (maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java:657), and its timeout scheduler (lines 974-988) polls `tryToTimeout` but is inert while the clock is zero. Consequence: `forkedProcessTimeoutInSeconds` does not bound a fork that hangs before emitting `TEST_SET_STARTING` (for example during provider discovery or static initialization). Expected behavior: arm a plugin-side deadline when the process is launched in `ForkStarter.fork`, independent of the first test-set event, while preserving the existing per-test-set timeout semantics. -- 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]
