[
https://jira.codehaus.org/browse/SUREFIRE-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341341#comment-341341
]
Kristian Rosenvold edited comment on SUREFIRE-1055 at 2/13/14 12:36 AM:
------------------------------------------------------------------------
When applying this technique to the sample project it is very easy to see that
the problem happens within the fork, not the reporting logic.
this means the bug is happening somewhere starting at ForkedBooter,
ForkingReporterFactor, probably closer to the junit4 provider itself. It
reproduces easily with the (excellent) test project !
was (Author: krosenvold):
When applying this techniquie to the sample project it is very easy to see that
the problem happens within the fork, not the reporting logic.
this means the bug is happening somewhere starting at ForkedBooter,
ForkingReporterFactor, probably closer to the junit4 provider itself. It
reproduces easily with the (excellent) test project !
> Parallel JUnit does not run all test methods with parallel=classesAndMethods
> perCoreThreadCount=false useUnlimitedThreads=true and threadCountMethods
> specified
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1055
> URL: https://jira.codehaus.org/browse/SUREFIRE-1055
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin
> Affects Versions: 2.16
> Reporter: Chris Hansen
> Attachments: surefire-output.txt
>
>
> Some test methods are skipped at random with the below configuration. When
> test methods are skipped in this way, only one method in the class runs.
> Running tests repeatedly with no code change often yields a different number
> of tests with each run (e.g. see the attached surefire-output.txt). Tests
> that take longer to run are less likely to be affected. This affects version
> 2.16 of Surefire and Failsafe equally.
> Here is a simple test project which reproduces the issue:
> https://github.com/hansenc/SUREFIRE-1055
> It has a few simple test classes with a naming convention for how many test
> methods are in each class (e.g. Methods4Test has 4 test methods).
> {code:xml}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.16</version>
> <configuration>
> <parallel>classesAndMethods</parallel>
> <perCoreThreadCount>false</perCoreThreadCount>
> <useUnlimitedThreads>true</useUnlimitedThreads>
> <threadCountMethods>3</threadCountMethods>
> </configuration>
> </plugin>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
