[jira] [Updated] (SUREFIRE-1789) inclusion using fully qualified class name is not respected
[
https://issues.apache.org/jira/browse/SUREFIRE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Lehky updated SUREFIRE-1789:
-
Description:
I am trying to use {{include}} configuration using fully qualified class name,
as described
[here|https://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html#Fully_qualified_class_name].
I have the following hierarchy in my test folder (showing only relevant parts):
{noformat}
src/test/java
+ features.feature_a
+- SomeStory.java
+ ignore.features.under_construction
+- AnotherStory.java
{noformat}
My pom configuration is:
{code:xml}
org.apache.maven.plugins
maven-failsafe-plugin
${surefire.plugin.version}
features.*.*Story
integration-test
verify
{code}
When I execute {{mvn verify}} both of the above Stories are run.
I am expecting that only "SomeStory" will be run. The other test
"AnotherStory", is not in the package "features.*".
was:
I am trying to use {{include}} configuration using fully qualified class name,
as described
[here|https://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html#Fully_qualified_class_name].
I have the following hierarchy in my test folder (showing only relevant parts):
{noformat}
+ features.feature_a
+- SomeStory.java
+ ignore.features.under_construction
+- AnotherStory.java
{noformat}
My pom configuration is:
{code:xml}
org.apache.maven.plugins
maven-failsafe-plugin
${surefire.plugin.version}
features.*.*Story
integration-test
verify
{code}
When I execute {{mvn verify}} both of the above Stories are run.
I am expecting that only "SomeStory" will be run. The other test
"AnotherStory", is not in the package "features.*".
> inclusion using fully qualified class name is not respected
> ---
>
> Key: SUREFIRE-1789
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1789
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 2.22.2
>Reporter: Mark Lehky
>Priority: Minor
>
> I am trying to use {{include}} configuration using fully qualified class
> name, as described
> [here|https://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html#Fully_qualified_class_name].
> I have the following hierarchy in my test folder (showing only relevant
> parts):
> {noformat}
> src/test/java
> + features.feature_a
> +- SomeStory.java
> + ignore.features.under_construction
> +- AnotherStory.java
> {noformat}
> My pom configuration is:
> {code:xml}
>
> org.apache.maven.plugins
> maven-failsafe-plugin
> ${surefire.plugin.version}
>
>
> features.*.*Story
>
>
>
>
>
> integration-test
> verify
>
>
>
>
> {code}
> When I execute {{mvn verify}} both of the above Stories are run.
> I am expecting that only "SomeStory" will be run. The other test
> "AnotherStory", is not in the package "features.*".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (SUREFIRE-1789) inclusion using fully qualified class name is not respected
Mark Lehky created SUREFIRE-1789:
Summary: inclusion using fully qualified class name is not
respected
Key: SUREFIRE-1789
URL: https://issues.apache.org/jira/browse/SUREFIRE-1789
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin, Maven Surefire Plugin
Affects Versions: 2.22.2
Reporter: Mark Lehky
I am trying to use {{include}} configuration using fully qualified class name,
as described
[here|https://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html#Fully_qualified_class_name].
I have the following hierarchy in my test folder (showing only relevant parts):
{noformat}
+ features.feature_a
+- SomeStory.java
+ ignore.features.under_construction
+- AnotherStory.java
{noformat}
My pom configuration is:
{code:xml}
org.apache.maven.plugins
maven-failsafe-plugin
${surefire.plugin.version}
features.*.*Story
integration-test
verify
{code}
When I execute {{mvn verify}} both of the above Stories are run.
I am expecting that only "SomeStory" will be run. The other test
"AnotherStory", is not in the package "features.*".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434065#comment-16434065
]
Mark Lehky commented on SUREFIRE-1480:
--
I updated my failsafe-plugin to latest (2.21.0) a few days ago and have not
seen this problem since. Maybe one of the surefire dependencies got updated? In
any case, I do not believe there is a point in pursuing this any further?
Perhaps [~hwentzke] has similar results?
> 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}
>
> {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)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428482#comment-16428482
]
Mark Lehky commented on SUREFIRE-1480:
--
I cannot get past the error, as above.
I do not understand how {{mvn install}} build passed, but then at *runtime* I
get "java.lang.Error: Unresolved compilation problems".
> 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}
>
> {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)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426353#comment-16426353
]
Mark Lehky commented on SUREFIRE-1480:
--
That was a total fail.
# I added some logging.
# I ran {{mvn -DskipTests -Dcheckstyle.skip install}}, which passed.
# Updated my project to use surefire 3.0.0-SNAPSHOT. I get:
{noformat}
[INFO] --- maven-failsafe-plugin:3.0.0-SNAPSHOT:integration-test (default) @
XXX-integrationtests ---
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 3.345 s
[INFO] Finished at: 2018-04-04T16:05:24-07:00
[INFO] Final Memory: 26M/409M
[INFO]
---
constituent[0]: file:/Users/mlehky/apache-maven-3.5.0/conf/logging/
constituent[1]: file:/Users/mlehky/apache-maven-3.5.0/lib/aopalliance-1.0.jar
constituent[2]: file:/Users/mlehky/apache-maven-3.5.0/lib/cdi-api-1.0.jar
constituent[3]: file:/Users/mlehky/apache-maven-3.5.0/lib/commons-cli-1.4.jar
constituent[4]: file:/Users/mlehky/apache-maven-3.5.0/lib/commons-io-2.5.jar
constituent[5]: file:/Users/mlehky/apache-maven-3.5.0/lib/commons-lang3-3.5.jar
constituent[6]: file:/Users/mlehky/apache-maven-3.5.0/lib/guava-20.0.jar
constituent[7]: file:/Users/mlehky/apache-maven-3.5.0/lib/guice-4.0-no_aop.jar
constituent[8]: file:/Users/mlehky/apache-maven-3.5.0/lib/jansi-1.13.jar
constituent[9]: file:/Users/mlehky/apache-maven-3.5.0/lib/javax.inject-1.jar
constituent[10]:
file:/Users/mlehky/apache-maven-3.5.0/lib/jcl-over-slf4j-1.7.22.jar
constituent[11]: file:/Users/mlehky/apache-maven-3.5.0/lib/jsr250-api-1.0.jar
constituent[12]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-artifact-3.5.0.jar
constituent[13]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-builder-support-3.5.0.jar
constituent[14]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-compat-3.5.0.jar
constituent[15]: file:/Users/mlehky/apache-maven-3.5.0/lib/maven-core-3.5.0.jar
constituent[16]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-embedder-3.5.0.jar
constituent[17]: file:/Users/mlehky/apache-maven-3.5.0/lib/maven-model-3.5.0.jar
constituent[18]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-model-builder-3.5.0.jar
constituent[19]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-plugin-api-3.5.0.jar
constituent[20]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-repository-metadata-3.5.0.jar
constituent[21]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-resolver-api-1.0.3.jar
constituent[22]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-resolver-connector-basic-1.0.3.jar
constituent[23]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-resolver-impl-1.0.3.jar
constituent[24]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-resolver-provider-3.5.0.jar
constituent[25]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-resolver-spi-1.0.3.jar
constituent[26]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-resolver-transport-wagon-1.0.3.jar
constituent[27]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-resolver-util-1.0.3.jar
constituent[28]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-settings-3.5.0.jar
constituent[29]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-settings-builder-3.5.0.jar
constituent[30]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-shared-utils-3.1.0.jar
constituent[31]:
file:/Users/mlehky/apache-maven-3.5.0/lib/maven-slf4j-provider-3.5.0.jar
constituent[32]:
file:/Users/mlehky/apache-maven-3.5.0/lib/org.eclipse.sisu.inject-0.3.3.jar
constituent[33]:
file:/Users/mlehky/apache-maven-3.5.0/lib/org.eclipse.sisu.plexus-0.3.3.jar
constituent[34]: file:/Users/mlehky/apache-maven-3.5.0/lib/plexus-cipher-1.7.jar
constituent[35]:
file:/Users/mlehky/apache-maven-3.5.0/lib/plexus-component-annotations-1.7.1.jar
constituent[36]:
file:/Users/mlehky/apache-maven-3.5.0/lib/plexus-interpolation-1.24.jar
constituent[37]:
file:/Users/mlehky/apache-maven-3.5.0/lib/plexus-sec-dispatcher-1.4.jar
constituent[38]:
file:/Users/mlehky/apache-maven-3.5.0/lib/plexus-utils-3.0.24.jar
constituent[39]: file:/Users/mlehky/apache-maven-3.5.0/lib/slf4j-api-1.7.22.jar
constituent[40]: file:/Users/mlehky/apache-maven-3.5.0/lib/wagon-file-2.12.jar
constituent[41]:
file:/Users/mlehky/apache-maven-3.5.0/lib/wagon-http-2.12-shaded.jar
constituent[42]:
file:/Users/mlehky/apache-maven-3.5.0/lib/wagon-provider-api-2.12.jar
---
Exception in thread "main" java.lang.Error: Unresolved compilation problems:
The import org.apache.maven.shared.utils.logging.MessageBuilder cannot
be resolved
The import org.apache.maven.shared.utils.logging.MessageUtils cannot be
resolved
MessageBuilder cannot be resolved to a type
[jira] [Comment Edited] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426273#comment-16426273
]
Mark Lehky edited comment on SUREFIRE-1480 at 4/4/18 10:36 PM:
---
I checked out the latest (3.0.0-SNAPSHOT), and from maven-surefire directory I
can {{mvn verify}} everything: "BUILD SUCCESS".
However, I cannot say the same from my IDE - I am an Eclipse guy. I get 138
errors. Any hints?
I can find the class you mentioned no problem. Does the surefire project use
any kind of a logger? For now I'm going to see how far I can get with just
{{System.out}}.
was (Author: mlehky):
I checked out the latest (3.0.0-SNAPSHOT), and from maven-surefire I can {{mvn
verify}} everything: "BUILD SUCCESS".
However, I cannot say the same from my IDE - I am an Eclipse guy. I get 138
errors. Any hints?
I can find the class you mentioned no problem. Does the surefire project use
any kind of a logger? For now I'm going to see how far I can get with just
{{System.out}}.
> 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}
>
> {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)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426273#comment-16426273
]
Mark Lehky commented on SUREFIRE-1480:
--
I checked out the latest (3.0.0-SNAPSHOT), and from maven-surefire I can {{mvn
verify}} everything: "BUILD SUCCESS".
However, I cannot say the same from my IDE - I am an Eclipse guy. I get 138
errors. Any hints?
I can find the class you mentioned no problem. Does the surefire project use
any kind of a logger? For now I'm going to see how far I can get with just
{{System.out}}.
> 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}
>
> {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)
[jira] [Comment Edited] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424217#comment-16424217
]
Mark Lehky edited comment on SUREFIRE-1480 at 4/3/18 4:41 PM:
--
Right now I have a testsuite of ~190 tests, that runs for ~5 hours, using 2
parallel threads, and reproduces this problem ~50% of the time. Yesterday I was
able to confirm that Jenkins is not a dependency - I can reproduce this problem
just running my testsuite from the CLI: {{mvn verify}}. The (perhaps)
interesting thing is that out of 13 test classes, only one ends up being
mangled each time. Different one each time, but only one.
I am still trying to create something smaller than 5 hours to reproduce this.
was (Author: mlehky):
Right now I have a testsuite of ~190 tests, that runs for ~5 hours, and
reproduces this problem ~50% of the time. Yesterday I was able to confirm that
Jenkins is not a dependency - I can reproduce this problem just running my
testsuite from the CLI: {{mvn verify}}. The (perhaps) interesting thing is that
out of 13 test classes, only one ends up being mangled each time. Different one
each time, but only one.
I am still trying to create something smaller than 5 hours to reproduce this.
> 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}
>
> {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)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424217#comment-16424217
]
Mark Lehky commented on SUREFIRE-1480:
--
Right now I have a testsuite of ~190 tests, that runs for ~5 hours, and
reproduces this problem ~50% of the time. Yesterday I was able to confirm that
Jenkins is not a dependency - I can reproduce this problem just running my
testsuite from the CLI: {{mvn verify}}. The (perhaps) interesting thing is that
out of 13 test classes, only one ends up being mangled each time. Different one
each time, but only one.
I am still trying to create something smaller than 5 hours to reproduce this.
> 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}
>
> {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)
[jira] [Commented] (SUREFIRE-1480) parallel tests may produce invalid .xml report
[
https://issues.apache.org/jira/browse/SUREFIRE-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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}
>
> {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)
[jira] [Created] (SUREFIRE-1480) parallel tests may produce invalid .xml report
Mark Lehky created SUREFIRE-1480:
Summary: 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: Maven Failsafe Plugin, Maven Surefire Plugin
Affects Versions: 2.20.1
Reporter: Mark Lehky
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}
{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)
[jira] [Created] (SUREFIRE-1423) empty excludes list in profile does not override excludes
Mark Lehky created SUREFIRE-1423:
Summary: empty excludes list in profile does not override excludes
Key: SUREFIRE-1423
URL: https://issues.apache.org/jira/browse/SUREFIRE-1423
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin, Maven Surefire Plugin
Affects Versions: 2.20
Reporter: Mark Lehky
I have a set of tests that I want to run by themselves and only sometime. I
defined my failsafe plugin as follows:
{noformat}
org.apache.maven.plugins
maven-failsafe-plugin
2.20
**/tests/dataload/**
integration-test
verify
{noformat}
I then defined a profile as follows:
{noformat}
run.dataload.tests
maven-failsafe-plugin
**/tests/dataload/**
{noformat}
Please note the empty {{}} tag in the profile. I was hoping this
would "remove" my excludes definition from the plugin definition. However, when
I run {{mvn -Prun.dataload.tests verify}} none of my tests are run.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
