[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361282#comment-361282
]
Alexander Ashitkin commented on MNG-5750:
-
Hello
first of all - thank you all for the such awesome tool like maven.
Regading the issue - we run builds for a week and results are great. it is 100%
stable now and artifacts are correct. Regarding the patch - i do understand it
is far from perfect. On other hand the changed code
*a* does not work as designed
*b* impacts build stability
In my eyes the patch is lesser of the evils and i recommend to implement the
fix asap. Please notice we were thinking to abondan concurrent build because of
the issue. I believe other users could do the same - try it, discover an issues
and abandon the feature.
@Kristian please clarify - is there any chance to productionize the patch in
the current form either need to wait for the proper fix? Any forecatsts are
very much appreciated.
thank you
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361121#comment-361121
]
Kristian Rosenvold commented on MNG-5750:
-
Please update this issue if the hangout comes to any noteworthy conclusion :)
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361102#comment-361102
]
Jason van Zyl commented on MNG-5750:
I think we should have a dev hangout dedicated to performance monitoring and
testing. Part of this includes concurrency issues so that the system can go
fast in parallel. Igor and I will eventually have to deal with this in our
large build but we are alleviating this issue right now by using a file-based
repository. We will soon a repository manager based system and we'll have to
flush this out. Our timeframe is the next 12 weeks. But I think a hangout topic
would be good. We have a harness for perf that I would likely to employ as
standard part of our build.
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361095#comment-361095
]
Kristian Rosenvold commented on MNG-5750:
-
This issue seems to be a bit of a hot potato. We need to find a better
solution, and I'm afraid it has to be somewhat more long-term than what
Alexander proposes, although it's a nice POC.
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361092#comment-361092
]
Jason van Zyl commented on MNG-5750:
It is always a good thing to run the integration tests with any patches. For
guidance you can look at:
http://takari.io/2014/06/01/contributing-to-maven-core.html
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361091#comment-361091
]
Alexander Ashitkin edited comment on MNG-5750 at 1/12/15 7:35 AM:
--
The fix worked for me. >30 builds succesfull builds in sequence. Based on
previous expirience i expected at lesat 5 failures here with ~100% probability.
Could somebody please provide some feedback and advise on the code change?
thank you
was (Author: alex_ashitkin):
The fix worked for me. >30 builds succesfull builds in sequence. Based on
previous expirience i expected at leat 5 failures here. Could somebody please
provide some feedback and advise on the code change?
thank you
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361091#comment-361091
]
Alexander Ashitkin edited comment on MNG-5750 at 1/12/15 7:26 AM:
--
The fix worked for me. >30 builds succesfull builds in sequence. Based on
previous expirience i expected at leat 5 failures here. Could somebody please
provide some feedback and advise on the code change?
thank you
was (Author: alex_ashitkin):
The fix worked for me. >30 builds succesfull builds in sequence. Based on
previous expirience i expected at leat 5 failures here. Could somebody please
provide some feedback and advise on the issue?
thank you
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361091#comment-361091
]
Alexander Ashitkin commented on MNG-5750:
-
The fix worked for me. >30 builds succesfull builds in sequence. Based on
previous expirience i expected at leat 5 failures here. Could somebody please
provide some feedback and advise on the issue?
thank you
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361074#comment-361074
]
Alexander Ashitkin commented on MNG-5750:
-
At the moment i suppose the problem is with
MojoExecutor#ensureDependenciesAreResolved, this place:
{code}
for ( MavenProject projectToResolve : projectsToResolve )
{
projectToResolve.setArtifactFilter( artifactFilter );
}
{code}
if intention is to reset filter before the resolved project build starts - it
doesnt work, the projects are being built concurrently.
I applied a local patch to workaround the issue and will come with results
later:
{code}
ArtifactFilter artifactFilter = getArtifactFilter( mojoDescriptor );
List projectsToResolve =
LifecycleDependencyResolver.getProjects(
session.getCurrentProject(), session,
mojoDescriptor.isAggregator() );
boolean skipFilterOnResolved =
Boolean.getBoolean("maven.MNG-5750.skipFilterOnResolved");
if (!skipFilterOnResolved) {
for ( MavenProject projectToResolve : projectsToResolve )
{
projectToResolve.setArtifactFilter( artifactFilter );
}
} else {
// this bracnh is triggered as workaround
System.err.println("recursive projectToResolve.setArtifactFilter(
artifactFilter ) skipped maven.MNG-5750.skipFilterOnResolved=true");
session.getCurrentProject().setArtifactFilter(artifactFilter);
}
{code}
thank you
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
> At this point the issue looks like problem with MavenProject#getArtifacts in
> concurrent builds.
> To help with the issue im happy to implement or evaluate any custom assembly
> to trace this down. Unfortunately i cannot submit my project - it is
> proprietary.
> Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361074#comment-361074
]
Alexander Ashitkin edited comment on MNG-5750 at 1/12/15 1:11 AM:
--
At the moment i suppose the problem is with
MojoExecutor#ensureDependenciesAreResolved, this place:
{code}
for ( MavenProject projectToResolve : projectsToResolve )
{
projectToResolve.setArtifactFilter( artifactFilter );
}
{code}
if intention is to reset filter before the resolved projects build starts - it
doesnt work, the projects are being built concurrently.
I applied a local patch to workaround the issue and will come with results
later:
{code}
ArtifactFilter artifactFilter = getArtifactFilter( mojoDescriptor );
List projectsToResolve =
LifecycleDependencyResolver.getProjects(
session.getCurrentProject(), session,
mojoDescriptor.isAggregator() );
boolean skipFilterOnResolved =
Boolean.getBoolean("maven.MNG-5750.skipFilterOnResolved");
if (!skipFilterOnResolved) {
for ( MavenProject projectToResolve : projectsToResolve )
{
projectToResolve.setArtifactFilter( artifactFilter );
}
} else {
// this bracnh is triggered as workaround
System.err.println("recursive projectToResolve.setArtifactFilter(
artifactFilter ) skipped maven.MNG-5750.skipFilterOnResolved=true");
session.getCurrentProject().setArtifactFilter(artifactFilter);
}
{code}
thank you
was (Author: alex_ashitkin):
At the moment i suppose the problem is with
MojoExecutor#ensureDependenciesAreResolved, this place:
{code}
for ( MavenProject projectToResolve : projectsToResolve )
{
projectToResolve.setArtifactFilter( artifactFilter );
}
{code}
if intention is to reset filter before the resolved project build starts - it
doesnt work, the projects are being built concurrently.
I applied a local patch to workaround the issue and will come with results
later:
{code}
ArtifactFilter artifactFilter = getArtifactFilter( mojoDescriptor );
List projectsToResolve =
LifecycleDependencyResolver.getProjects(
session.getCurrentProject(), session,
mojoDescriptor.isAggregator() );
boolean skipFilterOnResolved =
Boolean.getBoolean("maven.MNG-5750.skipFilterOnResolved");
if (!skipFilterOnResolved) {
for ( MavenProject projectToResolve : projectsToResolve )
{
projectToResolve.setArtifactFilter( artifactFilter );
}
} else {
// this bracnh is triggered as workaround
System.err.println("recursive projectToResolve.setArtifactFilter(
artifactFilter ) skipped maven.MNG-5750.skipFilterOnResolved=true");
session.getCurrentProject().setArtifactFilter(artifactFilter);
}
{code}
thank you
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
>
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361061#comment-361061
]
Alexander Ashitkin edited comment on MNG-5750 at 1/11/15 7:45 AM:
--
Some thughts on the root cause: #setArtifactsFilters seems to be caused by
following pattern: set empty filter before source mojo, it will create
#deepCopy with empty artifacts and that will trigger #setArtifactFilter
{code}
#setArtifactFilter null [another-module] [BuilderThread 2] [ashiale]
#getArtifacts artifactFilter == null || resolvedArtifacts == null, assigning
empty set another-module [another-module] [BuilderThread 8] [ashiale]
#getArtifacts [another-module] [BuilderThread 8] [ashiale]
at
org.apache.maven.project.MavenProject.getArtifacts(MavenProject.java:744)
at
org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1278)
at org.apache.maven.project.MavenProject.(MavenProject.java:201)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:295)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:247)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:216)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
#setArtifacts to [] [#getArtifactId==null] [BuilderThread 8] [ashiale]
at
org.apache.maven.project.MavenProject.setArtifacts(MavenProject.java:727)
at
org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1278)
at org.apache.maven.project.MavenProject.(MavenProject.java:201)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:295)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:247)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:216)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
#setArtifactFilter null [another-module] [BuilderThread 8] [ashiale]
#setArtifactFilter null [module-1] [BuilderThread 8] [ashiale]
#setArtifactFilter null [module-1] [BuilderThread 8] [ashiale]
#setArtifactFilter null [module-3] [BuilderThread 8] [ashiale]
...
#setArtifactFilter null [module-471] [BuilderThread 8] [ashiale]
{code}
was (Author: alex_ashitkin):
Some thughts on the root cause: #setArtifactsFilters seems to be caused by
following pattern: set empty filter before source mojo, it willcreate deepCopy
with empty artifacts and that will trigger #setArtifactFilter
{code}
#setArtifactFilter null [another-module] [BuilderThread 2] [ashiale]
#getArtifacts artifactFilter == null || resolvedArtifacts == null, assigning
empty set another-module [another-module] [BuilderThread 8] [ashiale]
#getArtifacts [another-module] [BuilderThread 8] [ashiale]
at
org.apache.maven.project.MavenProject.getArtifacts(MavenProject.java:744)
at
org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1278)
at org.apache.maven.project.MavenProject.(MavenProject.java:201)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:295)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:247)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:216)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
#setArtifacts to [] [ArtifactIdIsNull] [BuilderThread 8] [ashiale]
at
org.apache.maven.project.MavenProject.setArtifacts(MavenProject.java:727)
at
org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1278)
at org.apache.maven.project.MavenProject.(MavenProject.java:201)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:295)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:247)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:216)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
#setArtifactFilter null [another-module] [BuilderThread 8] [ashiale]
#setArtifactFilter null [module-1
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361061#comment-361061
]
Alexander Ashitkin commented on MNG-5750:
-
Some thughts on the root cause: #setArtifactsFilters seems to be caused by
following pattern: set empty filter before source mojo, it willcreate deepCopy
with empty artifacts and that will trigger #setArtifactFilter
{code}
#setArtifactFilter null [another-module] [BuilderThread 2] [ashiale]
#getArtifacts artifactFilter == null || resolvedArtifacts == null, assigning
empty set another-module [another-module] [BuilderThread 8] [ashiale]
#getArtifacts [another-module] [BuilderThread 8] [ashiale]
at
org.apache.maven.project.MavenProject.getArtifacts(MavenProject.java:744)
at
org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1278)
at org.apache.maven.project.MavenProject.(MavenProject.java:201)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:295)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:247)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:216)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
#setArtifacts to [] [ArtifactIdIsNull] [BuilderThread 8] [ashiale]
at
org.apache.maven.project.MavenProject.setArtifacts(MavenProject.java:727)
at
org.apache.maven.project.MavenProject.deepCopy(MavenProject.java:1278)
at org.apache.maven.project.MavenProject.(MavenProject.java:201)
at
org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:501)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:295)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.packageSources(AbstractSourceJarMojo.java:247)
at
org.apache.maven.plugin.source.AbstractSourceJarMojo.execute(AbstractSourceJarMojo.java:216)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
#setArtifactFilter null [another-module] [BuilderThread 8] [ashiale]
#setArtifactFilter null [module-1] [BuilderThread 8] [ashiale]
#setArtifactFilter null [module-1] [BuilderThread 8] [ashiale]
#setArtifactFilter null [module-3] [BuilderThread 8] [ashiale]
...
#setArtifactFilter null [module-471] [BuilderThread 8] [ashiale]
{code}
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level ~%20 of builds fail. To
> workaround the issue we reduced concurrency to 4 in development builds and
> reverted production build to 1 thread.
> Main point of failures:
> # Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points
> to a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
> # Compiler - unexpected failure because of incorrect classpath (literally all
> dependencies are not on the classpath), like: {code}
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
> does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
> org.joda.time does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static
> import only from classes and interfaces
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
> com.google.common.base does not exist
> 20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static
> import only from classes and interfaces
> {code}
> # Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
> plusgin seems to be also affected)
>
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361060#comment-361060
]
Alexander Ashitkin edited comment on MNG-5750 at 1/11/15 7:16 AM:
--
Have some findings here. I logged MavenProject access in case of sporadic
compilation failure:
{code}
#getArtifacts [failed-module] [BuilderThread 7] [ashiale]
#setArtifactFilter null [failed-module] [BuilderThread 7] [ashiale]
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @
failed-module ---
#setArtifactFilter
org.apache.maven.artifact.resolver.filter.CumulativeScopeArtifactFilter@3646a1
[failed-module] [BuilderThread 7] [ashiale]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
failed-module ---
#setArtifactFilter null [failed-module] [BuilderThread 5] [ashiale]
#getArtifacts [failed-module] [BuilderThread 7] [ashiale]
#getArtifacts artifactFilter == null || resolvedArtifacts == null, assigning
empty set failed-module [failed-module] [BuilderThread 7] [ashiale]
#getArtifacts artifactFilter == null || resolvedArtifacts == null, assigning
empty set failed-module [failed-module] [BuilderThread 7] [ashiale]
#getArtifacts [failed-module] [BuilderThread 7] [ashiale]
[INFO] Compiling 1 source file to ...\failed-module\target\test-classes
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile
(default-testCompile) on project failed-module: Compilation failure:
Compilation failure:
{code}
As you can see above, problematic module is being built with Thread 7, but
unexpecedly Thread 5 invokes setArtifactFilter breaking the flow. I tried to
trace BuilderThread 5 up. It finshed install task on an upstream module and
after that i see repeated invocations of setArtifactFilter null on the *ALL*
project modules (total 471 log entries of setArtifactFilter null on another
modules from thread 5):
{code}
#setArtifactFilter null [module-built-by-thread-5] [BuilderThread 5] [ashiale]
at
org.apache.maven.project.MavenProject.setArtifactFilter(MavenProject.java:1490)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:288)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
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:116)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @
module-built-by-thread-5 ---
[INFO] Installing .../module-built-by-thread-5-SNAPSHOT.jar
[INFO] Installing .../module-built-by-thread-5 -SNAPSHOT.pom
[INFO] Installing .../module-built-by-thread-5-SNAPSHOT-sources.jar
#setArtifactFilter null [root-parent] [BuilderThread 5] [ashiale]
at
org.apache.maven.project.MavenProject.setArtifactFilter(MavenProject.java:1490)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:288)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
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:116)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
{code}
This makes me think of the issue with post build actions - module build reset
artifatcs filter on all dependencies thus faiing the build
thank you
was (Author: alex_ashitkin):
Have some findings here:
This MavenProject access log followed by compilation failure:
{code}
#getArtifacts [failed-module] [BuilderThread 7] [ashiale]
#setArtifactFilter null [failed-module] [BuilderThread 7] [ashiale]
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @
failed-module ---
#setArtifactFilter
org.apache.maven.artifact.resolver.filter.CumulativeScopeArtifactFilter@3646a1
[failed-module] [BuilderThread 7] [ashiale]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
failed-module ---
#setArtifactFilter null [failed-module] [BuilderThread 5] [ashiale]
#getArtifacts [failed-mo
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361060#comment-361060
]
Alexander Ashitkin commented on MNG-5750:
-
Have some findings here:
This MavenProject access log followed by compilation failure:
{code}
#getArtifacts [failed-module] [BuilderThread 7] [ashiale]
#setArtifactFilter null [failed-module] [BuilderThread 7] [ashiale]
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @
failed-module ---
#setArtifactFilter
org.apache.maven.artifact.resolver.filter.CumulativeScopeArtifactFilter@3646a1
[failed-module] [BuilderThread 7] [ashiale]
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @
failed-module ---
#setArtifactFilter null [failed-module] [BuilderThread 5] [ashiale]
#getArtifacts [failed-module] [BuilderThread 7] [ashiale]
#getArtifacts artifactFilter == null || resolvedArtifacts == null, assigning
empty set failed-module [failed-module] [BuilderThread 7] [ashiale]
#getArtifacts artifactFilter == null || resolvedArtifacts == null, assigning
empty set failed-module [failed-module] [BuilderThread 7] [ashiale]
#getArtifacts [failed-module] [BuilderThread 7] [ashiale]
[INFO] Compiling 1 source file to ...\failed-module\target\test-classes
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile
(default-testCompile) on project failed-module: Compilation failure:
Compilation failure:
{code}
As you can see above, problematic module is being built with Thread 7, but
unexpecedly Thread 5 invokes setArtifactFilter breaking the flow. I tried to
trace BuilderThread 5 up. It finshed install task on an upstream module and
that i see repeated invocations of setArtifactFilter null on the *ALL* modules
(total 471 log entries of setArtifactFilter null on another modules from thread
5):
{code}
#setArtifactFilter null [module-built-by-thread-5] [BuilderThread 5] [ashiale]
at
org.apache.maven.project.MavenProject.setArtifactFilter(MavenProject.java:1490)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:288)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
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:116)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @
module-built-by-thread-5 ---
[INFO] Installing .../module-built-by-thread-5-SNAPSHOT.jar
[INFO] Installing .../module-built-by-thread-5 -SNAPSHOT.pom
[INFO] Installing .../module-built-by-thread-5-SNAPSHOT-sources.jar
#setArtifactFilter null [root-parent] [BuilderThread 5] [ashiale]
at
org.apache.maven.project.MavenProject.setArtifactFilter(MavenProject.java:1490)
at
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:288)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
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:116)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
at
org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
{code}
This makes me think of the issue with post buildactions - module build reset
artifatcs filter on all dependencies thus faiing the build
thank you
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single thr
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Ashitkin updated MNG-5750:
Description:
We have a large project of 300+ modules which regularly fails with different
kind of errors in different places. The issue is reliably reproduced with
parallel build and is not happens in single threaded. The optimal concurrency
level for our project ~10 threads. At this level ~%20 of builds fail. To
workaround the issue we reduced concurrency to 4 in development builds and
reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# Compiler - unexpected failure because of incorrect classpath (literally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly
plusgin seems to be also affected)
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
was:
We have a large project of 300+ modules which regularly fails with different
kind of errors in different places. The issue is reliably reproduced with
parallel build and is not happens in single threaded. The optimal concurrency
level for our project ~10 threads. At this level ~%20 of builds fail. To
workaround the issue we reduced concurrency to 4 in development builds and
reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# Compiler - unexpected failure because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly seems
to be also affected)
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. A
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Ashitkin updated MNG-5750:
Description:
We have a large project of 300+ modules which regularly fails with different
kind of errors in different places. The issue is reliably reproduced with
parallel build and is not happens in single threaded. The optimal concurrency
level for our project ~10 threads. At this level ~%20 of builds fail. To
workaround the issue we reduced concurrency to 4 in development builds and
reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# Compiler - unexpected failure because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# Jar - unexpected NPE. Reported with stack traces in MJAR-192. (assembly seems
to be also affected)
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
was:
We have a large project of 300+ modules which regularly fails with different
kind of errors in different places. The issue is reliably reproduced with
parallel build and is not happens in single threaded. The optimal concurrency
level for our project ~10 threads. At this level ~%20 of builds fail. To
workaround the issue we reduced concurrency to 4 in development builds and
reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# unexpected compilation failures because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# unexpected NPE in archiver plugins, eg jar, assembly. Reported with stack
traces in MJAR-192
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads. At this level
[jira] (MNG-5750) Sporadic failures in concurrent build
[
https://jira.codehaus.org/browse/MNG-5750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Ashitkin updated MNG-5750:
Description:
We have a large project of 300+ modules which regularly fails with different
kind of errors in different places. The issue is reliably reproduced with
parallel build and is not happens in single threaded. The optimal concurrency
level for our project ~10 threads. At this level ~%20 of builds fail. To
workaround the issue we reduced concurrency to 4 in development builds and
reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# unexpected compilation failures because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# unexpected NPE in archiver plugins, eg jar, assembly. Reported with stack
traces in MJAR-192
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
was:
We have a large project of 300+ modules which regularly fails with different
kind of classloading issues in different places. The issue is reliably
reproduced only with parallel build and is not happens in single threaded. The
optimal concurrency level for our project ~10 threads. At this level ~%20 of
builds fail. To workaround the issue we reduced concurrency to 4 in development
builds and reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# unexpected compilation failures because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# unexpected NPE in archiver plugins, eg jar, assembly. Reported with stack
traces in MJAR-192
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
> Sporadic failures in concurrent build
> -
>
> Key: MNG-5750
> URL: https://jira.codehaus.org/browse/MNG-5750
> Project: Maven
> Issue Type: Bug
> Components: General
>Affects Versions: 3.1.1, 3.2.1, 3.2.2, 3.2.5
> Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
> HotSpot JDK 7u25
> windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
>Reporter: Alexander Ashitkin
>Priority: Critical
>
> We have a large project of 300+ modules which regularly fails with different
> kind of errors in different places. The issue is reliably reproduced with
> parallel build and is not happens in single threaded. The optimal concurrency
> level for our project ~10 threads.
[jira] (MNG-5750) Sporadic failures in concurrent build
Alexander Ashitkin created MNG-5750:
---
Summary: Sporadic failures in concurrent build
Key: MNG-5750
URL: https://jira.codehaus.org/browse/MNG-5750
Project: Maven
Issue Type: Bug
Components: General
Affects Versions: 3.2.5, 3.2.2, 3.2.1, 3.1.1
Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux Oracle
HotSpot JDK 7u25
windows server 2008 x64 Oracle HotSpot JDK 7u65/8u25
Reporter: Alexander Ashitkin
Priority: Critical
We have a large project of 300+ modules which regularly fails with different
kind of classloading issues in different places. The issue is reliably
reproduced only with parallel build and is not happens in single threaded. The
optimal concurrency level for our project ~10 threads. At this level ~%20 of
builds fail. To workaround the issue we reduced concurrency to 4 in development
builds and reverted production build to 1 thread.
Main point of failures:
# Surefire ClassNotFound. Reported and investigated in SUREFIRE-1132. Points to
a problem with MavenProject#getArtifacts - empty set unexpectedly returned.
# unexpected compilation failures because of incorrect classpath (lterally all
dependencies are not on the classpath), like: {code}
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[3,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[4,30] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[8,25] package ...
does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[9,21] package
org.joda.time does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[11,1] static import
only from classes and interfaces
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,37] package
com.google.common.base does not exist
20:20:54 [ERROR] /D:/jenkins/work/workspace/..Request.java:[12,1] static import
only from classes and interfaces
{code}
# unexpected NPE in archiver plugins, eg jar, assembly. Reported with stack
traces in MJAR-192
At this point the issue looks like problem with MavenProject#getArtifacts in
concurrent builds.
To help with the issue im happy to implement or evaluate any custom assembly to
trace this down. Unfortunately i cannot submit my project - it is proprietary.
Thanks in advance, Alexander
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
