|
||||||||||||
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 |
- [JIRA] (JENKINS-15466) Fatal Error No Cl... all.in.one.th...@gmail.com (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... h.schm...@tfe.nl (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... mikko.tapani...@nokia.com (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... h.schm...@tfe.nl (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... pjdar...@java.net (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... pjdar...@java.net (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... jgl...@cloudbees.com (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... pjdar...@java.net (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... pixma...@gmail.com (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... m...@hanabi.se (JIRA)
- [JIRA] (JENKINS-15466) Fatal Error ... jgl...@cloudbees.com (JIRA)
I suspect that this is (yet another) case of Windows being a bit non-deterministic - we had this bug happening @work and rebooting the slave made the problem go away, but the slaves get rebooted regularly anyway...
As a workaround, I'd suggest that the code drop back to the "old fashioned" way of comparing the canonical path to absolute path if the Windows-specific code fails.
This is what I'm doing at work now - as this is an intermittant issue it is difficult to be certain that this change had fixed it completely, but I am sure that it's no worse.
I've attached a patch that does this workaround.