Clebert Suconic created SUREFIRE-2186:
-----------------------------------------
Summary: Leaks in Surefire when reusing the fork
Key: SUREFIRE-2186
URL: https://issues.apache.org/jira/browse/SUREFIRE-2186
Project: Maven Surefire
Issue Type: Bug
Reporter: Clebert Suconic
It is not possible to run a very extensive test suite with the current version
of surefire when you reuse the forks.
In ActiveMQ Artemis, we have thousands of integration tests and we reuse the
forks otherwise it would take an infinite amount of time to complete the test
suite.
org.apache.maven.surefire.api.util.internal.ClassMethod is being held by
ClassMethodIndexer, which is being held by Junit4RunListener.
Also, a bit scary the fact that ClassMethodIndexer is using a non static
ThreadLocal. even though this is not causing this particular leak, but since my
complain is the test suite not being able to finish with the new SureFire maybe
this is also causing issues.
I have been doing fine on pursuing leaks (even though it's not my main
professional attribution :) but I created a pet project just for that purpose,
if someone is interested in fixing this I will be certainly up to help fixing
or even fixing it myself if I'm provided some guidance as I'm new to this
codebase)
To reproduce the ClassMethod leak validation, you should follow these steps:
git clone https://github.com/clebertsuconic/surefire-reproducer.git
cd surefire-reproducer
mvn install
Notice there might be other leaks like the one I mentioned with the non static
ThreadLocal
which by the way is an anti-pattern. For example:
https://errorprone.info/bugpattern/ThreadLocalUsage
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
