maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@codehaus.org>
Subject [jira] (SUREFIRE-1132) Surefire: regular isolated classloader failures in parallelbuild
Date Sat, 03 Jan 2015 21:51:10 GMT

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

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

I guess you can download and install sources @2.19-SNAPSHOT and debug the surefire.
You can change the version if needed (version-plugin)
https://github.com/apache/maven-surefire/archive/master.zip

Of course use the same version in your build as the installed one.

Run the build
{code}mvnDebug test -Dmaven.surefire.debug=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000{code}

Suppose the forkCount=1.

Then in IDEA, Run/Debug Configurations > + > Remote > change to port 8000
Go to console. If you see halting maven process with something like Listening to port ...,
then start remote debugging in IDEA, repeat again if wants to connect or if failed to connect.

> 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
>         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
>            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)

Mime
View raw message