[
https://jira.codehaus.org/browse/SUREFIRE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358774#comment-358774
]
Roy Arnon commented on SUREFIRE-1122:
-------------------------------------
@Tibor I checkout out the source for failsafe to see if I could maybe submit a
patch.
>From what I saw, it seems that report is generated twice - once when the first
>run of all tests is complete, and then again after the flaky test is completed.
So the file is generated twice, the second time containing only the test that
was run again.
The line that is called twice is in ForkClient.java:
{code:java}
case ForkingRunListener.BOOTERCODE_TESTSET_COMPLETED:
getOrCreateReporter( channelNumber ).testSetCompleted( createReportEntry(
remaining ) );
break;
{code}
No idea how to fix this though, as this seems like a difficult issue - the
testSetCompleted event I'm assuming should only be fired once per test run no?
> When running failsafe with -Dfailsafe.rerunFailingTestsCount and parallel
> all, the reports are not generated correctly
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: SUREFIRE-1122
> URL: https://jira.codehaus.org/browse/SUREFIRE-1122
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
> Affects Versions: 2.18
> Reporter: Roy Arnon
> Assignee: Tibor Digana
> Attachments: invalid.xml, test.zip, valid.xml
>
>
> Hi,
> I just tried the new feature -Dfailsafe.rerunFailingTestsCount on our
> failsafe build.
> Unfortunately, when running the build using parallel=all, it seems the junit
> xml files are not generated correctly.
> I've tried running it multiple different ways, including classedAndMethods,
> and all, but it seems to generate an incorrect xml file either way.
> I've attached both files here.
> I can provide a pom and java test case if required.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
