www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-6218) Jenkins - Bunch of Apache Camel builds end up with some weird Jenkins/Maven exceptions/errors.
Date Tue, 31 Dec 2013 03:29:54 GMT

    [ https://issues.apache.org/jira/browse/INFRA-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859290#comment-13859290
] 

Gavin commented on INFRA-6218:
------------------------------

" Failed to deploy artifacts:" has absolutely nothing to do with the original query why this
ticket was opened. in fact I see no mention of it over the last 8 months until today !! How
can you relate this to this ticket I have no idea.

The 2nd error you mention about "heap space" is also brand new and YES as I hinted IS to do
with ARM.

So yes I claim this ticket FIXED - please now follow up any questions to the builds@ mailing
list like I said. 
I will not respond further to this FIXED ticket.

> 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
>         Attachments: Bildschirmfoto 2013-05-14 um 18.06.38.png, Camel-2.10.x_build_237_Jenkins_log.txt,
Camel.trunk.fulltest-1339-console.txt, Camel.trunk.fulltest.java7-608-console .txt, Camel.trunk.fulltest.java7-616-console.txt,
Camel.trunk.fulltest.java7-870-console.txt, Camel.trunk.notest-1873-console .txt, Camel.trunk.notest-1890-console.txt,
sling-trunk-1.6-failures.zip
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message