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

IOException: Unable to delete <FileName> on Windows Slaves

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Component/s: core
    • Environment:
      Server: Ubuntu 2.6.35-28-server
      Slaves: Windows Server 2008 RC2
    • Similar Issues:

      Description

      We have updated our Jenkins Server from 1.474 to 1.477 last week and since then have an increasing number of failing jobs caused by an IOException. Our jobs are configured to clean and checkout the project at start and clean the workspace at the end of the job. Sometimes the failure occures at the end (Run1 and Run2) and sometime right after start execution (Run3). I have attached the logs from different jobs.

      We have 5 slaves with Windows Server 2008 RC2 and the failure occures on all of them. Actually we are cleaning the workspace by hand so that the jobs could start executing the build but failing at the final clean up, so many of our jobs are running red at the moment but building correctly.

        Attachments

        1. Build-Run1.log
          8 kB
        2. Build-Run2.log
          6 kB
        3. Build-Run3.log
          29 kB

          Issue Links

            Activity

            swoeste Sebastian Woeste created issue -
            swoeste Sebastian Woeste made changes -
            Field Original Value New Value
            Description We have updated our Jenkins Server from 1.474 to 1.477 last week and since then have an increasing number of failing jobs caused by an IOException. Our jobs are configured to clean and checkout the project at start and clean the workspace at the end of the job. Sometimes the failure occures at the end (Run1 and Run2) and sometime right after start execution (Run3). I have attached the logs from different jobs.

            We have 5 slaves with Windows Server 2008 RC2 and the failure occures on all of them. Actually we are cleaning the workspace by hand so that the jobs could start executing the build but failing and the final clean up, so many of our jobs are running red at the moment but building correctly.
            We have updated our Jenkins Server from 1.474 to 1.477 last week and since then have an increasing number of failing jobs caused by an IOException. Our jobs are configured to clean and checkout the project at start and clean the workspace at the end of the job. Sometimes the failure occures at the end (Run1 and Run2) and sometime right after start execution (Run3). I have attached the logs from different jobs.

            We have 5 slaves with Windows Server 2008 RC2 and the failure occures on all of them. Actually we are cleaning the workspace by hand so that the jobs could start executing the build but failing at the final clean up, so many of our jobs are running red at the moment but building correctly.
            azschorn Andreas Zschorn made changes -
            Link This issue duplicates JENKINS-15418 [ JENKINS-15418 ]
            baranov Valentin Baranov made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            danielbeck Daniel Beck made changes -
            Link This issue duplicates JENKINS-15331 [ JENKINS-15331 ]
            danielbeck Daniel Beck made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Duplicate [ 3 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 145509 ] JNJira + In-Review [ 191520 ]

              People

              • Assignee:
                Unassigned
                Reporter:
                swoeste Sebastian Woeste
              • Votes:
                10 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: