[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420919#comment-16420919
]
Mark Lehky commented on SUREFIRE-1480:
--------------------------------------
[~tibor17] As per
http://maven.apache.org/surefire/maven-failsafe-plugin/source-repository.html I
tried:
{code}
$ git clone --branch surefire-2.21.0_vote-1
https://git-wip-us.apache.org/repos/asf/maven-surefire.git
Cloning into 'maven-surefire'...
fatal: repository 'https://git-wip-us.apache.org/repos/asf/maven-surefire.git/'
not found
{code}
:(
Instead I guessed:
{code}
$ git clone g...@github.com:apache/maven-surefire.git
$ cd maven-surefire/maven-failsafe-plugin
$ git checkout surefire-2.21.0_vote-1
{code}
So what am I looking at now? Not sure where to start.
> parallel tests may produce invalid .xml report
> ----------------------------------------------
>
> Key: SUREFIRE-1480
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1480
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin,
> Maven Surefire Plugin
> Affects Versions: 2.20.1
> Reporter: Mark Lehky
> Priority: Major
> Attachments: FailedXMLReport.txt, Stacktrace_failedTest.txt
>
>
> Relevant software:
> * Jenkins 2.108
> * Maven 3.??
> * JUnit 4.12
> * maven-failsafe-plugin 2.20.1 (I have seen this issue with surefire as well)
> I have a testsuite (one JUnit class) that contains multiple tests (multiple
> JUnit methods), which are all run in parallel. Some of the tests may be
> ignore using JUnit {{Assume}}.
> On occasion (not 100% reproducible), the resulting report will contain an
> entry like:
> {noformat}
> < message="Skip test!">
> {noformat}
> The correct entry, as is produced most of the time, should be:
> {noformat}
> <skipped message="Skip test!"/>
> {noformat}
> The invalid formatted XML, when run in Jenkins, results in the test being
> flagged as failed, and Jenkins simply has the message:
> "TEST-....xml.[failed-to-read]" (the dots are replaced with the correct
> filename!).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
