Hello, I've tried with several projects and functionally, everything seems OK.
However, I noticed certain slowdown in case multiple forks are beings used to run the tests. After some investigation, it seems one of the forked VMs gets "stuck" for about 30s before it gets shutdown. So every surefire:test or failsafe:test run results in 30s delay (if multiple forks were used). I've created a simple reproducer - https://github.com/psiroky/surefire-2_20-slowdown-reproducer . When running "mvn clean test -s settings.xml" you can see the 30s waiting after the tests were executed. The repo also contains thread dumps for both the main Maven process and the surefire's ForkedBooter. I am running on Fedora 25 + JDK 8u121. Tried with Maven 3.2.5 and the staged 3.5.0. Can someone confirm the above, or is just some quirk in my local env? Thanks, Petr On Tue, Apr 4, 2017 at 10:13 PM Tibor Digana <tibordig...@apache.org> wrote: > Hi, > > We solved 65 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12334636 > > There are still a couple of issues left in JIRA: > > https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC > > Staging repo: > https://repository.apache.org/content/repositories/maven-1328/ > > https://repository.apache.org/content/repositories/maven-1328/org/apache/maven/surefire/surefire/2.20/surefire-2.20-source-release.zip > > Source release checksum(s): > surefire-2.20-source-release.zip sha1: > 100e4074a819ed1f8aecb94ef2a71c3c818ec542 > > Staging site: > http://maven.apache.org/surefire-archives/surefire-LATEST/ > > Guide to testing staged releases: > http://maven.apache.org/guides/development/guide-testing-releases.html > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > Cheers > Tibor >
