|
||||||||
|
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-14628) Fatal error on J... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)
- [JIRA] (JENKINS-14628) Fatal error... [email protected] (JIRA)

Same issue with xUnity 1.47 and Jenkins 1.477. Downgrade to xUnit 1.46 seem to fix after a full restart of Jenkins.
Shouldn't this be tagged 'xunit'?