• Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • jacoco-plugin
    • Jenkins ver. 1.609

      Hello,

      We have an issue where our Maven builds run for a little while, then at some point a new build will kick off and will not be able to clean the workspace because jacoco.exec is locked and can not be deleted. Our build user "BuildProp" is an administrator on this server and cannot remove the file.

      If I log in as myself, also and Admin, I can delete the file. However, once I navigate away from the folder and back, jacoco.exec will once again appear.

      This started about a week ago, I suspect is has something to do with us running builds on a slave node.

      Started by an SCM change
      Building on master in workspace d:\jwsp\GIT.build1-maven3-develop
      Wiping out workspace first.
      java.nio.file.DirectoryNotEmptyException: d:\jwsp\GIT.build1-maven3-develop\abc\Apps\applications\Reconfirm\target
      at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
      at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source)
      at java.nio.file.Files.delete(Unknown Source)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at hudson.Util.deleteFile(Util.java:247)
      at hudson.FilePath.deleteRecursive(FilePath.java:1202)
      at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211)
      at hudson.FilePath.deleteRecursive(FilePath.java:1193)
      at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211)
      at hudson.FilePath.deleteRecursive(FilePath.java:1193)
      at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211)
      at hudson.FilePath.deleteRecursive(FilePath.java:1193)
      at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211)
      at hudson.FilePath.deleteRecursive(FilePath.java:1193)
      at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211)
      at hudson.FilePath.access$1100(FilePath.java:191)
      at hudson.FilePath$15.invoke(FilePath.java:1185)
      at hudson.FilePath$15.invoke(FilePath.java:1182)
      at hudson.FilePath.act(FilePath.java:989)
      at hudson.FilePath.act(FilePath.java:967)
      at hudson.FilePath.deleteContents(FilePath.java:1182)
      at hudson.plugins.git.extensions.impl.WipeWorkspace.beforeCheckout(WipeWorkspace.java:28)
      at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1013)
      at hudson.scm.SCM.checkout(SCM.java:484)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1270)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531)
      at hudson.model.Run.execute(Run.java:1741)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:374)
      Archiving artifacts
      Skipping sonar analysis due to bad build status FAILURE
      Notified Stash for commit with id e3f3c786a74c4be6eec44e5771650a8a0d1737cd
      Email was triggered for: Failure - Any
      Sending email for trigger: Failure - Any

          [JENKINS-28636] Jacoco.exec can not be deleted

          centic added a comment -

          I quickly checked for file handle leaks, but could not find any obvious ones.

          Which version of jacoco-plugin is this?

          You can try to use https://github.com/kohsuke/file-leak-detector on the Jenkins Slave to see if there are file handles still open and where they were allocated?

          centic added a comment - I quickly checked for file handle leaks, but could not find any obvious ones. Which version of jacoco-plugin is this? You can try to use https://github.com/kohsuke/file-leak-detector on the Jenkins Slave to see if there are file handles still open and where they were allocated?

          mcraig88, is this still an issue?

          Martin Heinzerling added a comment - mcraig88 , is this still an issue?

          centic added a comment -

          No response for a long time, therefore closing for now. Please reopen with some updated information if this is still an issue for you.

          centic added a comment - No response for a long time, therefore closing for now. Please reopen with some updated information if this is still an issue for you.

            mcraig88 Mike Craig
            mcraig88 Mike Craig
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: