|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
David Humeniuk I believe that stack trace is different than the other stack traces reported in this bug report. It seems to be similar to the stack trace in JENKINS-21914. In both cases, the problem is visible on Windows.
Can you confirm that there are no "orphan" git.exe processes running on the machine which shows the problem?
If there are orphan git processes, can you kill them and see if that resolves your issue?