StefanPenndorf commented on issue #2049: URL: https://github.com/apache/maven-surefire/issues/2049#issuecomment-3362104659
Hi, I can also confirm the issue. Due to a wrong (too short) configuration for `forkedProcessTimeoutInSeconds` we had builds failing on CI (Jenkins) with the message "There was a timeout in the fork" in `VerifyMojo`. The parameter `forkedProcessTimeoutInSeconds` was set to 300s (5 Minutes) by accident but our test suite ran about 2 hours successfully without any test failures. After 2h and a successfull test run our build suddenly failed in verify phase with "There was a timeout in the fork" but no error message during tests. It took us long time to connect the timeout error with the `forkedProcessTimeoutInSeconds=300` setting. While `forkedProcessTimeoutInSeconds` has no effect on the forked test process this setting is useless. We'll remove this setting from our Maven configuration until this bug has been resolved. In the far past (10y+) this setting worked and helped us killing tests hanging due to problems in the setup of integration tests with fast feedback. -- 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]
