maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Commented: (MSUREFIRE-65) Surefire causes OOM
Date Thu, 09 Mar 2006 15:27:23 GMT
    [ ] 

Brett Porter commented on MSUREFIRE-65:

BTW, to those testing it do either:
a) add this to your POM

(there are reportedly still some problems doing it this way)


b) build it. But make sure you use -Dmaven.test.skip=true the first time
on surefire itself as the old plugin tries to use the new classes which
don't match.

you need to first build the surefire-testng branch, and then the maven-surefire-plugin-testng


> Surefire causes OOM
> -------------------
>          Key: MSUREFIRE-65
>          URL:
>      Project: Maven 2.x Surefire Plugin
>         Type: Bug

>     Versions: 2.1.1
>     Reporter: Mike Perham
>      Fix For: 2.2

> We have a build with 30-40 modules which use JUnit to run a heavy load of database integration
testing.  Our build has never worked with just 'mvn clean install' since 2.0 - we get OOM
errors within 5-10 modules (even with -Xmx512m).  When I enable the test skip flag, the entire
build runs to completion.  I suspect there is a memory leak somewhere in surefire or its classloader
where things are not getting freed after each module's test run.  We are currently using surefire-plugin
2.1.1 since 2.1.2 has MSUREFIRE-59.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message