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

Jobs failing with cannot delete directory error

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • p4-plugin
    • Jenkins ver 2.89.3 (OS X); p4-plugin ver 1.8.4; Windows slave - Windows 7 Professional SP1

      Jobs on our Windows slave machine are often failing with an "Unable to delete directory" error. The directory isn't locked, etc. and a subsequent run may succeed. This happens with various jobs and with different directories. It just started occurring within the last week. No backups are running during the build. We have tried updating Jenkins and the P4 plug-in, as well as Perforce on the slave machine to no avail. Any suggestions or workarounds would be appreciated. 

       

      P4 Task: attempt: 1
      P4 Task: failed: java.io.IOException: Unable to delete directory <path_to_file>.
      ERROR: P4 Task: failed: java.io.IOException: Unable to delete directory <path_to_file>.

          [JENKINS-49168] Jobs failing with cannot delete directory error

          Karl Wirth added a comment -

          If you have a support contract please contact support@perforce.com so I can investigate further. Note that if this isn't a permissions error then we are going to need something like Windows process monitor to see what's happening to these directories when we are trying to delete them. Initial thoughts are another job, some background thread still has a lock on the directory or AV software.

          Karl Wirth added a comment - If you have a support contract please contact support@perforce.com so I can investigate further. Note that if this isn't a permissions error then we are going to need something like Windows process monitor to see what's happening to these directories when we are trying to delete them. Initial thoughts are another job, some background thread still has a lock on the directory or AV software.

          Karl Wirth added a comment -

          No response so closing for now. Happy to investigate further if this is still a problem.

          Karl Wirth added a comment - No response so closing for now. Happy to investigate further if this is still a problem.

          Karl Wirth added a comment -

          No response so closing for now. Happy to investigate further if this is still a problem.

          Karl Wirth added a comment - No response so closing for now. Happy to investigate further if this is still a problem.

            Unassigned Unassigned
            arlyn R S
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: