[SUREFIRE-2023] The integration test Surefire946KillMainProcessInReusableForkIT hanged and timed out because SIGTERM happened before the first test has started. The plugin should be able to terminate itself whenever after SIGTERM.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-M6
• Component/s: Maven Failsafe Plugin, Maven Surefire Plugin
• External issue URL: https://github.com/apache/maven-surefire/runs/5168696705?check_suite_focus=true
• Assignee: Tibor Digana
• Reporter: Tibor Digana
• Created: 23/Feb/22 15:29
• Updated: 23/Feb/22 23:54
• Resolved: 23/Feb/22 23:53

Description

[INFO] Running org.apache.maven.surefire.its.jiras.Surefire946KillMainProcessInReusableForkIT
Error:  Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 107.514 s <<< FAILURE! - in org.apache.maven.surefire.its.jiras.Surefire946KillMainProcessInReusableForkIT
Error:  org.apache.maven.surefire.its.jiras.Surefire946KillMainProcessInReusableForkIT.test[exit-kill]  Time elapsed: 31.379 s  <<< ERROR!
org.junit.runners.model.TestTimedOutException: test timed out after 60000 milliseconds
	at app/surefire.its@3.0.0-M6-SNAPSHOT/org.apache.maven.surefire.its.jiras.Surefire946KillMainProcessInReusableForkIT.test(Surefire946KillMainProcessInReusableForkIT.java:111)

The test has timed out 60 seconds.
2022-02-12T19:44:53.470
2022-02-12T19:46:00.745

The shutdown hoot is registered on fork startup.
The fork has started and no shutdown Thread could break the fork because the SIGTERM signal was received by the JVM before the fork has started.