[
https://jira.codehaus.org/browse/SUREFIRE-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358891#comment-358891
]
Andreas Gudian commented on SUREFIRE-1122:
------------------------------------------
~hellspam, your test case is really good.
Just to let you know, I've boiled it down to using just the surefire-plugin,
forkCount=0, parallel=classes (with only one class to execute, there is nothing
actually done in parallel) - and I can see the same result as you. Without
parallel=..., but still with hard-configured Junit47 provider, the report looks
fine.
I need to dig in some more, but won't have much more time today. I'll still try
to get it done for the bugfix release that Tibor wants to roll next week.
> 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: Andreas Gudian
> 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)
