[jira] [Created] (SUREFIRE-2195) Surefire reports are not correct when running tests in parallel using JUnit5
Debraj Manna created SUREFIRE-2195:
--
Summary: Surefire reports are not correct when running tests in
parallel using JUnit5
Key: SUREFIRE-2195
URL: https://issues.apache.org/jira/browse/SUREFIRE-2195
Project: Maven Surefire
Issue Type: Bug
Components: JUnit 5.x support
Affects Versions: 3.1.2, 3.0.0-M7
Reporter: Debraj Manna
Attachments: image.png
The issue has been discussed in the [Maven mailing
list|https://lists.apache.org/thread/6k10kmxzz75rz8mqn3pl1ltvfltw87m9]. I am
creating a bug here as suggested in the mailing list
Cross-posting it here for completeness
My {{junit-platform.properties}} looks like below
{code:java}
junit.jupiter.execution.parallel.enabled=true
junit.jupiter.execution.parallel.config.strategy=fixed
junit.jupiter.execution.parallel.config.fixed.parallelism=8
junit.jupiter.execution.parallel.mode.default=same_thread
junit.jupiter.execution.parallel.mode.classes.default=concurrent
{code}
I am observing the surefire reports that are getting generated are not correct
I have a test class named
{{com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest}}
contains just a single test, {{testAirTicketing()}}.
But in the report file,
TEST-com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest.xml.
I see like below
{code:xml}
http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd";
version="3.0"
name="com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest"
time="44.711" tests="2" errors="1" skipped="0" failures="0”>
…
[jira] [Updated] (SUREFIRE-2195) Surefire reports are not correct when running tests in parallel using JUnit5
[
https://issues.apache.org/jira/browse/SUREFIRE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Debraj Manna updated SUREFIRE-2195:
---
Description:
The issue has been discussed in the [Maven mailing
list|https://lists.apache.org/thread/6k10kmxzz75rz8mqn3pl1ltvfltw87m9]. I am
creating a bug here as suggested in the mailing list
Cross-posting it here for completeness
My {{junit-platform.properties}} looks like below
{code:java}
junit.jupiter.execution.parallel.enabled=true
junit.jupiter.execution.parallel.config.strategy=fixed
junit.jupiter.execution.parallel.config.fixed.parallelism=8
junit.jupiter.execution.parallel.mode.default=same_thread
junit.jupiter.execution.parallel.mode.classes.default=concurrent
{code}
I am observing the surefire reports that are getting generated are not correct
I have a test class named
{{com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest}}
contains just a single test, {{testAirTicketing()}}.
But in the report file,
TEST-com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest.xml.
I see like below
{code:xml}
http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd";
version="3.0"
name="com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest"
time="44.711" tests="2" errors="1" skipped="0" failures="0”>
…
https://lists.apache.org/thread/6k10kmxzz75rz8mqn3pl1ltvfltw87m9]. I am
creating a bug here as suggested in the mailing list
Cross-posting it here for completeness
My {{junit-platform.properties}} looks like below
{code:java}
junit.jupiter.execution.parallel.enabled=true
junit.jupiter.execution.parallel.config.strategy=fixed
junit.jupiter.execution.parallel.config.fixed.parallelism=8
junit.jupiter.execution.parallel.mode.default=same_thread
junit.jupiter.execution.parallel.mode.classes.default=concurrent
{code}
I am observing the surefire reports that are getting generated are not correct
I have a test class named
{{com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest}}
contains just a single test, {{testAirTicketing()}}.
But in the report file,
TEST-com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest.xml.
I see like below
{code:xml}
http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd";
version="3.0"
name="com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest"
time="44.711" tests="2" errors="1" skipped="0" failures="0”>
…
https://issues.apache.org/jira/browse/SUREFIRE-2195
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
>Affects Versions: 3.0.0-M7, 3.1.2
>Reporter: Debraj Manna
>Priority: Major
> Attachments: image.png
>
>
> The issue has been discussed in the [Maven mailing
> list|https://lists.apache.org/thread/6k10kmxzz75rz8mqn3pl1ltvfltw87m9]. I am
> creating a bug here as suggested in the mailing list
> Cross-posting it here for completeness
> My {{junit-platform.properties}} looks like below
> {code:java}
> junit.jupiter.execution.parallel.enabled=true
> junit.jupiter.execution.parallel.config.strategy=fixed
> junit.jupiter.execution.parallel.config.fixed.parallelism=8
> junit.jupiter.execution.parallel.mode.default=same_thread
> junit.jupiter.execution.parallel.mode.classes.default=concurrent
> {code}
> I am observing the surefire reports that are getting generated are not correct
> I have a test class named
> {{com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest}}
> contains just a single test, {{testAirTicketing()}}.
> But in the report file,
> TEST-com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest.xml.
>
> I see like below
> {code:xml}
> http://www.w3.org/2001/XMLSchema-instance";
> xsi:noNamespaceSchemaLocation="https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd";
> version="3.0"
> name="com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest"
> time="44.711" tests="2" errors="1" skipped="0" failures="0”>
> …
>classname="com.spotnana.servicetests.analytics.ingestion.pnr.AirServiceTest"
> time="5.789"/>
>classname="com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest"
> time="33.331”>
> {code}
> It seems to be picking tests from some other class like {{AirServiceTest}} as
> in this case.
> The console logs are also not correct. Please check the attached screenshot.
> In the attached screenshot of the console logs, it is saying {{Test Run 5}}
> but the {{AirInvoiceServiceTest}} contains only 1 test. And also the report
> shows random data. For example, sometimes it says {{Test Run 5}} , sometimes
> it says {{Test Run 2}
[jira] [Commented] (SUREFIRE-2195) Surefire reports are not correct when running tests in parallel using JUnit5
[
https://issues.apache.org/jira/browse/SUREFIRE-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766769#comment-17766769
]
Debraj Manna commented on SUREFIRE-2195:
[~zoltan.meze] Is it possible to share your custom XML reporter and the steps
on how to use it, so that I can also use it?
> Surefire reports are not correct when running tests in parallel using JUnit5
>
>
> Key: SUREFIRE-2195
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2195
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support
>Affects Versions: 3.0.0-M7, 3.1.2
>Reporter: Debraj Manna
>Priority: Major
> Attachments: image.png
>
>
> The issue has been discussed in the [Maven mailing
> list|https://lists.apache.org/thread/6k10kmxzz75rz8mqn3pl1ltvfltw87m9]. I am
> creating a bug here as suggested in the mailing list
> Cross-posting it here for completeness
> My {{junit-platform.properties}} looks like below
> {code:java}
> junit.jupiter.execution.parallel.enabled=true
> junit.jupiter.execution.parallel.config.strategy=fixed
> junit.jupiter.execution.parallel.config.fixed.parallelism=8
> junit.jupiter.execution.parallel.mode.default=same_thread
> junit.jupiter.execution.parallel.mode.classes.default=concurrent
> {code}
> I am observing the surefire reports that are getting generated are not correct
> I have a test class named
> {{com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest}}
> contains just a single test, {{testAirTicketing()}}.
> But in the report file,
> TEST-com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest.xml.
>
> I see like below
> {code:xml}
> http://www.w3.org/2001/XMLSchema-instance";
> xsi:noNamespaceSchemaLocation="https://maven.apache.org/surefire/maven-surefire-plugin/xsd/surefire-test-report-3.0.xsd";
> version="3.0"
> name="com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest"
> time="44.711" tests="2" errors="1" skipped="0" failures="0”>
> …
>classname="com.spotnana.servicetests.analytics.ingestion.pnr.AirServiceTest"
> time="5.789"/>
>classname="com.spotnana.servicetests.backoffice.invoicing.AirInvoiceServiceTest"
> time="33.331”>
> {code}
> It seems to be picking tests from some other class like {{AirServiceTest}} as
> in this case.
> The console logs are also not correct. Please check the attached screenshot.
> In the attached screenshot of the console logs, it is saying {{Test Run 5}}
> but the {{AirInvoiceServiceTest}} contains only 1 test. And also the report
> shows random data. For example, sometimes it says {{Test Run 5}} , sometimes
> it says {{Test Run 2}}, etc.
> I am observing it as part of a big project consistently with every run. I am
> trying to reproduce it in a small example. If I am able to do I will share
> it. In the mean time if some debug logs are needed, let me know I will be
> happy to share them.
> Junit5 Version - 5.9.3
> I am observing the issue with Junit5 Version 5.10.0 also. I tried reducing
> the {{junit.jupiter.execution.parallel.config.fixed.parallelism}} to 3 but
> there also I am getting the same problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-5315) Artifact resolution sporadically fails in parallel builds
[
https://issues.apache.org/jira/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052837#comment-16052837
]
Debraj Manna commented on MNG-5315:
---
I am also seeing the same issue with maven 3.5.0 while doing {{mvn clean
package -T 4 -DskipTests}}
> Artifact resolution sporadically fails in parallel builds
> -
>
> Key: MNG-5315
> URL: https://issues.apache.org/jira/browse/MNG-5315
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.4
>Reporter: Ivan Dubrov
>Assignee: Jason van Zyl
>Priority: Minor
> Fix For: Issues to be reviewed for 4.x
>
> Attachments: MNG-5315-3.0.x.patch, MNG-5315-3.1.2-SNAPSHOT.patch
>
>
> Artifact resolution can fail during the parallel build if it was downloaded
> during the same session.
> Scenario:
> 1) Delete the whole Maven local repository.
> 2) Run build "mvn compile -T1.5C"
> 3) Build fails (see log extracts below)
> 4) If I run build again, it succeeds.
> It seems like the problem is due to two thread trying to resolve same
> artifact concurrently. This problem never happens once I have all
> dependencies cached in the local repository.
> Extracts from the log output:
> {noformat}Downloading:
> http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
> 12444/13937 KB ...
> ...
> [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2,
> already updated during this session.
> [DEBUG] Skipped remote update check for
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this
> session.
> [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4,
> already updated during this session.
> [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4,
> already updated during this session.
> ...
> [ERROR] Failed to execute goal on project util: Could not resolve
> dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The
> following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2,
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0,
> org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to
> find commons-cli:commons-cli:jar:1.2 in
> http://nexus/content/repositories/thirdparty was cached in the local
> repository, resolution will not be reattempted until the update interval of
> gw.thirdparty has elapsed or updates are forced -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project util: Could not resolve dependencies for project
> com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not
> be resolved: commons-cli:commons-cli:jar:1.2,
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0,
> org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to
> find commons-cli:commons-cli:jar:1.2 in
> http://nexus/content/repositories/thirdparty was cached in the local
> repository, resolution will not be reattempted until the update interval of
> gw.thirdparty has elapsed or updates are forced
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.la
[jira] [Created] (MBUILDCACHE-110) Maven Build Cache Extension forcing a dependency on plexus-utils in plugin execution
Debraj Manna created MBUILDCACHE-110: Summary: Maven Build Cache Extension forcing a dependency on plexus-utils in plugin execution Key: MBUILDCACHE-110 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-110 Project: Maven Build Cache Extension Issue Type: Bug Affects Versions: 1.2.0 Reporter: Debraj Manna I am observing specific plugin like [protobuf-maven-plugin|https://github.com/ascopes/protobuf-maven-plugin] is breaking with `maven-build-cache` extension 1.2. It is due to `plexus-utils`. The issue was discussed in the plugin forum # [https://github.com/ascopes/protobuf-maven-plugin/discussions/470|https://github.com/ascopes/protobuf-maven-plugin/discussions/470https://github.com/ascopes/protobuf-maven-plugin/issues/472] # [https://github.com/ascopes/protobuf-maven-plugin/issues/472|https://github.com/ascopes/protobuf-maven-plugin/discussions/470https://github.com/ascopes/protobuf-maven-plugin/issues/472] I was asked to raise an issue here in the `protobuf-maven-plugin` group. So doing the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MBUILDCACHE-110) Maven Build Cache Extension forcing a dependency on plexus-utils in plugin execution
[ https://issues.apache.org/jira/browse/MBUILDCACHE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908153#comment-17908153 ] Debraj Manna commented on MBUILDCACHE-110: -- [~kriegaex] Updated the description and fixed the links. > Maven Build Cache Extension forcing a dependency on plexus-utils in plugin > execution > > > Key: MBUILDCACHE-110 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-110 > Project: Maven Build Cache Extension > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Debraj Manna >Priority: Minor > > I am observing specific plugin like > [protobuf-maven-plugin|https://github.com/ascopes/protobuf-maven-plugin] is > breaking with `maven-build-cache` extension 1.2. It is due to `plexus-utils`. > The issue was discussed in the plugin forum > # > [https://github.com/ascopes/protobuf-maven-plugin/discussions/470|https://github.com/ascopes/protobuf-maven-plugin/discussions/470] > # > [https://github.com/ascopes/protobuf-maven-plugin/issues/472|https://github.com/ascopes/protobuf-maven-plugin/discussions/472] > > I was asked to raise an issue here in the `protobuf-maven-plugin` group. So > doing the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MBUILDCACHE-110) Maven Build Cache Extension forcing a dependency on plexus-utils in plugin execution
[ https://issues.apache.org/jira/browse/MBUILDCACHE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Debraj Manna updated MBUILDCACHE-110: - Description: I am observing specific plugin like [protobuf-maven-plugin|https://github.com/ascopes/protobuf-maven-plugin] is breaking with `maven-build-cache` extension 1.2. It is due to `plexus-utils`. The issue was discussed in the plugin forum # [https://github.com/ascopes/protobuf-maven-plugin/discussions/470|https://github.com/ascopes/protobuf-maven-plugin/discussions/470] # [https://github.com/ascopes/protobuf-maven-plugin/issues/472|https://github.com/ascopes/protobuf-maven-plugin/discussions/472] I was asked to raise an issue here in the `protobuf-maven-plugin` group. So doing the same. was: I am observing specific plugin like [protobuf-maven-plugin|https://github.com/ascopes/protobuf-maven-plugin] is breaking with `maven-build-cache` extension 1.2. It is due to `plexus-utils`. The issue was discussed in the plugin forum # [https://github.com/ascopes/protobuf-maven-plugin/discussions/470|https://github.com/ascopes/protobuf-maven-plugin/discussions/470https://github.com/ascopes/protobuf-maven-plugin/issues/472] # [https://github.com/ascopes/protobuf-maven-plugin/issues/472|https://github.com/ascopes/protobuf-maven-plugin/discussions/470https://github.com/ascopes/protobuf-maven-plugin/issues/472] I was asked to raise an issue here in the `protobuf-maven-plugin` group. So doing the same. > Maven Build Cache Extension forcing a dependency on plexus-utils in plugin > execution > > > Key: MBUILDCACHE-110 > URL: https://issues.apache.org/jira/browse/MBUILDCACHE-110 > Project: Maven Build Cache Extension > Issue Type: Bug >Affects Versions: 1.2.0 >Reporter: Debraj Manna >Priority: Minor > > I am observing specific plugin like > [protobuf-maven-plugin|https://github.com/ascopes/protobuf-maven-plugin] is > breaking with `maven-build-cache` extension 1.2. It is due to `plexus-utils`. > The issue was discussed in the plugin forum > # > [https://github.com/ascopes/protobuf-maven-plugin/discussions/470|https://github.com/ascopes/protobuf-maven-plugin/discussions/470] > # > [https://github.com/ascopes/protobuf-maven-plugin/issues/472|https://github.com/ascopes/protobuf-maven-plugin/discussions/472] > > I was asked to raise an issue here in the `protobuf-maven-plugin` group. So > doing the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
