maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason van Zyl (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5750) Sporadic failures in concurrent build
Date Mon, 12 Jan 2015 15:43:18 GMT

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

Mime
View raw message