[ 
https://issues.apache.org/jira/browse/SUREFIRE-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana updated SUREFIRE-2023:
-----------------------------------
    Description: 
{noformat}
[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)
{noformat}


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.

  was:

{noformat}
[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)
{noformat}


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.
No fork has started and no shutdown Thread could break the fork.


> 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.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-2023
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-2023
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>            Priority: Major
>             Fix For: 3.0.0-M6
>
>         Attachments: 2022-02-12T19-44-50_418-jvmRun1.dump, 
> 2022-02-12T19-44-50_418-jvmRun1.dumpstream, 
> 2022-02-12T19-44-50_418.dumpstream, log.txt
>
>
> {noformat}
> [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)
> {noformat}
> 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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to