|
||||||||
|
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-16298) DRY FATAL: null j... [email protected] (JIRA)
- [JIRA] (JENKINS-16298) DRY FATAL: nul... [email protected] (JIRA)
- [JIRA] (JENKINS-16298) DRY FATAL: nul... [email protected] (JIRA)
- [JIRA] (JENKINS-16298) DRY FATAL: nul... [email protected] (JIRA)
- [JIRA] (JENKINS-16298) DRY FATAL: nul... [email protected] (JIRA)
- [JIRA] (JENKINS-16298) DRY FATAL: nul... [email protected] (JIRA)
- [JIRA] (JENKINS-16298) DRY FATAL: nul... [email protected] (JIRA)
I tried to reproduce that problem, but had no success so far. From the exception it is hard to see where it actually crashed.
How big is the dry-warnings.xml file in the build folder on your machine? Can you try to lower the number of lines that identify a warning in simian? Just to see if the total number of warnings cause that problem...