Adam Lerman created SUREFIRE-1327:
-------------------------------------

             Summary: Allow failed tests to run in new fork when using 
reuseForks and rerunFailingTestsCount
                 Key: SUREFIRE-1327
                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1327
             Project: Maven Surefire
          Issue Type: Improvement
          Components: Maven Failsafe Plugin, Maven Surefire Plugin
    Affects Versions: 2.19.1
         Environment: CentOS
Maven 3.3.3
            Reporter: Adam Lerman
            Priority: Minor


Our project has 102 modules and 1000+ test classes. We use forkCount=1C and 
reuseForks=false as there are a few places in our project that use static 
variables and setting reuseForks to true causes tests failures. I would like to 
be able to reuseForks as it cuts significant time (30% or so) off the build, 
but hunting down the broken tests becomes a problem. I propose that when using 
rerunFailingTestsCount the runner should spawn a new fork for failed tests to 
ensure the test did not fail due to a dirty fork



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to