Am 02/20/17 um 01:10 schrieb Tibor Digana: > I meant this build which is in good conditions > https://builds.apache.org/view/Maven%20Master%20Release%20Status/job/maven-master-release-status-test-surefire-linux/30/console
This points to a console with IT failures. That build never succeeded on Jenkins. There had been issues with the setup of those jobs. That should be solved. It does not show the issues we are seeing on the BSDs. That's what I am referring to with "is only reproducible on *BSD." Here is a build job showing the issue exists on those others OSes as well. <https://builds.apache.org/view/Maven%20Master%20Release%20Status/job/maven-master-release-status-test-plugins-windows/58/console> >From the maven-assembly-plugin: [INFO] Building: projects\descriptor-refs\jar-with-dependencies\deps-unpacked-to-root-dir\pom.xml [INFO] ..FAILED (7.6 s) You need to log into Jenkins to see the build.log from the workspace. That build.log contained that "Did not properly say good bye." message from surefire. I just restarted that job due to this, so that build.log will have disappeared already. It should run successfully. There are no plugin ITs failing on windows. Reading the Surefire FAQ on this issue, it states that this may happen when something runs out of resources etc. This led to pull request <https://github.com/apache/maven-surefire/pull/144>. Although real resource leaks, I doubt it's the OS running out of resources producing that message. Regards, -- Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
