Thanks Niclas and Sebb On Sun, Oct 17, 2010 at 5:40 PM, Niklas Gustavsson <nik...@protocol7.com> wrote: > On Sun, Oct 17, 2010 at 12:27 PM, sebb <seb...@gmail.com> wrote: >> Note that Java on Windows locks jars on the classpath, so it could be >> that there is a stale process which still has the file open. > > As Sebb noted, there is a stale JVM holding on to that file (and a lot > of other Apache DS jars). It was started on October 13 (now seems to > be deleted in Hudson), with the following command line: > c:\hudson\tools\java\latest-1.6-64\jre\bin\java -Xmx1024m -jar > C:\Users\hudson\AppData\Local\Temp\surefirebooter6057665385176864901.jar > C:\Users\hudson\AppData\Local\Temp\surefire4636072868886298356tmp > C:\Users\hudson\AppData\Local\Temp\surefire846828774278823902tmp > > In the directory: > C:\hudson\hudson-slave\workspace\dir-apacheds-jdk16-win\trunk\server-integ\ > > Not sure if this helps you track down what part of the build which > causes this behavior.
At least it's a starting point. Last night the build started again and while building the server-integ module (that contains our integration test) the surefire process was killed after 15 minutes. Running org.apache.directory.server.suites.StockServerISuite Process 1287375949406 is killed. ... Process timeout out after 900 seconds So I guess there is another stale JVM process, could you kill it once again? I disabled the job and will investigate the problem offline. Thanks, Stefan
