Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55478

CompositeIOException when deleting workspace before check-out

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None
    • Jenkins 2.157

      A downgrade to 2.156 resolved this issue.

      Stack trace:

      Build wurde zeitgesteuert ausgelöst.
      [EnvInject] - Loading node environment variables.
      Baue auf dem Agenten „
      hb-build-java
      " in Arbeitsbereich /home/jenkins/workspace/MMD-2.1-trunk
      Cleaning local Directory ./
      jenkins.util.io.CompositeIOException: Unable to delete '/home/jenkins/workspace/MMD-2.1-trunk/.'. Tried 3 times (of a maximum of 3) waiting 0,1 Sekunden between attempts.
      at jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:84)
      at hudson.Util.deleteContentsRecursive(Util.java:244)
      at hudson.scm.subversion.CheckoutUpdater$SubversionUpdateTask.perform(CheckoutUpdater.java:93)
      at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:168)
      at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1041)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:1017)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:990)
      at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3086)
      at hudson.remoting.UserRequest.perform(UserRequest.java:212)
      at hudson.remoting.UserRequest.perform(UserRequest.java:54)
      at hudson.remoting.Request$2.run(Request.java:369)
      at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      at java.lang.Thread.run(Thread.java:748)
      Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to hb-build-java
      at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
      at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
      at hudson.remoting.Channel.call(Channel.java:957)
      at hudson.FilePath.act(FilePath.java:1072)
      at hudson.FilePath.act(FilePath.java:1061)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:937)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:864)
      at hudson.scm.SCM.checkout(SCM.java:504)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
      at hudson.model.Run.execute(Run.java:1810)
      at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
      at hudson.model.ResourceController.execute(ResourceController.java:97)
      at hudson.model.Executor.run(Executor.java:429)

          [JENKINS-55478] CompositeIOException when deleting workspace before check-out

          Matt Sicker added a comment -

          Do you have any logs from the agent? A CompositeIOException should print out all its IOExceptions during the stack trace, but it doesn't look like that works properly via remoting.

          Also, do you know whether or not the directory exists? Specific reproduction steps would help a lot.

          Matt Sicker added a comment - Do you have any logs from the agent? A CompositeIOException should print out all its IOExceptions during the stack trace, but it doesn't look like that works properly via remoting. Also, do you know whether or not the directory exists? Specific reproduction steps would help a lot.

          I can reproduce it with 2.157 but can not find any logs on agent side. Please advice how to get them. The agent ist connected via SSH. host.log Please find enclosed the whole host log.

          Michael Sanders added a comment - I can reproduce it with 2.157 but can not find any logs on agent side. Please advice how to get them. The agent ist connected via SSH. host.log Please find enclosed the whole host log.

          Matt Sicker added a comment -

          Ok, based on those logs, I have a hypothesis:

          Previously, when retrying a delete, if the previous retry had an error, but then the current retry works, this will still throw an exception for the prior issue. If this is the case, then it might be a rather simple fix for all the related regressions here.

          Matt Sicker added a comment - Ok, based on those logs, I have a hypothesis: Previously, when retrying a delete, if the previous retry had an error, but then the current retry works, this will still throw an exception for the prior issue. If this is the case, then it might be a rather simple fix for all the related regressions here.

          Ah! This issue seems to be fixed with 2.159. Tests were successful. Thank you sir.

          Michael Sanders added a comment - Ah! This issue seems to be fixed with 2.159. Tests were successful. Thank you sir.

          Matt Sicker added a comment -

          Yes, we reverted the problem, and I have updated code for the original problem to be merged for the next weekly release.

          Matt Sicker added a comment - Yes, we reverted the problem, and I have updated code for the original problem to be merged for the next weekly release.

            jvz Matt Sicker
            msanders Michael Sanders
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: