You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jörg Hohwiller (JIRA)" <ji...@apache.org> on 2016/07/12 21:27:20 UTC

[jira] [Created] (SUREFIRE-1261) surefire hangs of failed tests and keeps lock on surefirebooter on Windows preventing clean

Jörg Hohwiller created SUREFIRE-1261:
----------------------------------------

             Summary: surefire hangs of failed tests and keeps lock on surefirebooter on Windows preventing clean
                 Key: SUREFIRE-1261
                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1261
             Project: Maven Surefire
          Issue Type: Bug
          Components: Maven Surefire Plugin, process forking
    Affects Versions: 2.19.1, 2.17
         Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Maven home: C:\project\software\maven
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: C:\project\software\java\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "dos"
            Reporter: Jörg Hohwiller


I have Spring-Tests run with surefire in a plain commandline maven build on windows. For whatever reason many tests fail with spring initialization exception. If I cancel the build in this case ([ctrl][c]) and then restart a clean build maven failes to delete the target directory. Using sysinternal tools I traced down that a java.exe process is hanging that locks a JAR called surefirebooter located in target. This is IMHO the forked process from the maven surefire plugin that was not terminated properly when the maven process was cancelled. 

You might need to register a shutdown hook in maven-surefire that properly cleans up the forked process. But this is just a brute guess...

http://stackoverflow.com/questions/17465117/maven-surefirebooter



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)