[ 
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360891#comment-360891
 ] 

Tibor Digana commented on SUREFIRE-1132:
----------------------------------------

I was fixing MavenProject.class in https://github.com/apache/maven/pull/34
We agreed with Jason to wait for immutable objects in maven-core, and not to 
push my temporary fix for MavenProject.class.
In case of MavenProject#getArtifacts(), that's Maven Core code. If you are sure 
about that, then the bug should belong to https://jira.codehaus.org/browse/MNG
Optionally you may watch the discussions in maven mailinglist
http://maven.40175.n5.nabble.com/Maven-Developers-f142166.html
and two discussions related in the sense of concurrency issues
http://maven.40175.n5.nabble.com/Formal-verification-of-thread-correctness-in-maven-core-td5822508.html
http://maven.40175.n5.nabble.com/GitHub-maven-pull-request-Improved-visibility-of-collections-and-variabl-td5821775.html
That's maximum I can help now.

Cheers

> Surefire: regular isolated classloader failures in parallelbuild
> ----------------------------------------------------------------
>
>                 Key: SUREFIRE-1132
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1132
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: classloading
>    Affects Versions: 2.17, 2.18.1
>         Environment: SLES 3.0.80-0.7-default SMP x86_64 GNU/Linux
> windows server 2008 x64
> Maven 3.2.2, 3.2.3, 3.2.5
> Oracle HotSpot JDK 7u25/7u65/8u25
>            Reporter: Alexander Ashitkin
>            Assignee: Tibor Digana
>         Attachments: consoleText-1.txt, consoleText-2.txt, consoleText-3.txt
>
>
> We have a large project of 300+ modules which regularly fails with different 
> kind of classloading issues in different places in surefire plugin. The issue 
> is reproduced only with parallel build and is not reproduced in single 
> threaded. This is a main contributor in build instability for us. All the not 
> loaded dependnecies are actually present in dependency tree. I attached 3 
> different samples of how build fails.
> Surefire config:
> {code}
>                     <configuration>
>                         <forkCount>0</forkCount>
>                         <!--doesnt work in parrallel build. Causes build 
> failures with error java.io.IOException: Stream Closed-->                     
>  <redirectTestOutputToFile>false</redirectTestOutputToFile>
>                         <useManifestOnlyJar>false</useManifestOnlyJar>
>                     </configuration>
> {code}
> maven cmd is like install -T 10
>  Please advise how to sort this out - ready to run any provided diagnostic 
> and evaluate any options.
> Thanks in advance, Alexander



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to