You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2013/07/09 22:19:51 UTC
[jira] [Commented] (INFRA-6218) Jenkins - Bunch of Apache Camel
builds end up with some weird Jenkins/Maven exceptions/errors.
[ https://issues.apache.org/jira/browse/INFRA-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703740#comment-13703740 ]
Robert Munteanu commented on INFRA-6218:
----------------------------------------
This seems to be a problem affecting multiple projects, additionally to Camel and Sling
- Stanbol - http://mail-archives.apache.org/mod_mbox/stanbol-dev/201305.mbox/%3C622119818.3620.1368710480549.JavaMail.hudson@aegis%3E
- Accumulo - http://mail-archives.apache.org/mod_mbox/accumulo-notifications/201305.mbox/%3C1994069866.850.1368024940264.JavaMail.hudson@aegis%3E
- James - http://james.10919.n7.nabble.com/Build-failed-in-Jenkins-james-mailet-2066-td49602.html
- Axis - http://axis.8716.n7.nabble.com/Build-failed-in-Jenkins-Axis2-trunk-java-1-6-1628-td113074.html
- ActiveMQ - http://activemq.2283324.n4.nabble.com/Build-failed-in-Jenkins-ActiveMQ-Apollo-Deploy-404-td4667759.html
- Flume - http://markmail.org/message/jbmcf63htel3fjbe
For Sling this has happened on most ( maybe all ) of the ubuntu slaves, and especially on Java 6 ; it did happen once on Java 7. The common links seem to be
- Maven projects
- Multi-module builds
> Jenkins - Bunch of Apache Camel builds end up with some weird Jenkins/Maven exceptions/errors.
> ----------------------------------------------------------------------------------------------
>
> Key: INFRA-6218
> URL: https://issues.apache.org/jira/browse/INFRA-6218
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Jenkins
> Reporter: Babak Vahdat
> Assignee: Jake Farrell
> Attachments: Bildschirmfoto 2013-05-14 um 18.06.38.png, Camel.trunk.fulltest-1339-console.txt, Camel.trunk.fulltest.java7-608-console .txt, Camel.trunk.fulltest.java7-616-console.txt, Camel.trunk.notest-1873-console .txt, Camel.trunk.notest-1890-console.txt
>
>
> Recently we're extremely suffering from different weird errors of Apache Camel builds. In many cases Jenkins says "Ping time out" and gives up the build process so we end up again & again with broken and incomplete builds shown with red bubbles, following two examples:
> https://builds.apache.org/job/Camel.trunk.fulltest/1324/console
> https://builds.apache.org/job/Camel.trunk.fulltest.java7/591/console
> And the corresponding Jenkins output in console:
> U camel-core/pom.xml
> U tooling/apt/src/main/java/org/apache/camel/tools/apt/EndpointAnnotationProcessor.java
> FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
> hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
> at hudson.remoting.Request.call(Request.java:174)
> at hudson.remoting.Channel.call(Channel.java:672)
> at hudson.FilePath.act(FilePath.java:854)
> at hudson.FilePath.act(FilePath.java:838)
> at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
> ...
> Or sometimes the build ends up with some wired Jenkins internal errors as you see here:
> https://builds.apache.org/job/Camel.trunk.fulltest.java7/582/console
> And the corresponding Jenkins output in console:
> [JENKINS] Archiving disabled
> [JENKINS] Archiving disabled
> Waiting for Jenkins to finish collecting data
> mavenExecutionResult exceptions not empty
> message : Internal error: java.lang.reflect.UndeclaredThrowableException
> cause : null
> Stack trace :
> org.apache.maven.InternalErrorException: Internal error: java.lang.reflect.UndeclaredThrowableException
> at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> No idea if all these has to do with the recent Jenkins upgrades @ INFRA. In all cases this is really annoying and currently almost all our builds end up with red bubbles.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira