[
https://jira.codehaus.org/browse/SUREFIRE-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360860#comment-360860
]
Tibor Digana commented on SUREFIRE-1132:
----------------------------------------
not necessary to use if ( file.exists() ), because isFile and isDirectory
internally performs exists() and some native calls as well.
So you need only the body of the branch and you may print + e: file.exists().
The IsolatedCL has a method like addUrl(). You may log this for the interest
what's coming inside the ICL.
You may log the boolean parame of IsolatedCL constructor. Then we would have
almost all.
{code}
if ( file.exists() )
{
System.err.println( url + "f:" + file.isFile()
+ " d:" + file.isDirectory() + " r:" +
file.canRead() );
}
{code}
> 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
> 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)
