[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.

[email protected] (JIRA) Thu, 12 Nov 2015 16:10:46 -0800

Title: Message Title

Jesse Glick commented on

JENKINS-29713

No clue offhand. Unfortunately the presence of a file does not indicate what code created it. If you have any idea how to reproduce from scratch, let me know. Or if it only happens in a particular system, but you are able to clone that into a test environment, you can try disabling other plugins to see if one of them is responsible.

It is possible, but rather difficult, to patch Java to give you a stack trace when a file is written. The File Leak Detector plugin tracks the events but normally discards the information when the file handle is closed. You can try running the following (untested!) in /script after installing that plugin:

 
                                                    org.kohsuke.file_leak_detector.ActivityListener.LIST.add(new org.kohsuke.file_leak_detector.ActivityListener() {
  public void open(Object obj, File file) {
    if (file.name == 'TASKMANAGER_IT_WORKFLOW_PoC@2') {
      java.util.logging.Logger.getLogger('JENKINS-29713').log(java.util.logging.Level.WARNING, null, new IllegalStateException())
    }
  }
})
 
                                                

and then check /log/all for a stack trace if it happens again.

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.

Reply via email to