[ https://issues.jboss.org/browse/JBIDE-13355?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13355: ------------------------------------------- Long story short, it's the deletes when the tests try to clean up after themselves that are causing issues. I suspect the only way around it will be to totally restructure the tests. But it's an intermittent failure. IBM has run into it: http://www-01.ibm.com/support/docview.wss?uid=swg21316377 Spring has run into it: https://issuetracker.springsource.com/browse/STS-3007?page=com.atlassian.... Sonatype has run into it: https://issues.sonatype.org/browse/MNGECLIPSE-1809 If it's intermittent, as it appears to be on Jenkins, can we simply kick off a new build until it all works fine? We can certainly look at revising the tests in github to try and avoid this, but I'd just as soon not reinvent the wheel with redoing tests on 3.3.x too. -- 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