maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Ashitkin (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5750) Sporadic failures in concurrent build
Date Fri, 16 Jan 2015 09:06:18 GMT

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

Mime
View raw message