You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2013/05/14 17:29:16 UTC

[jira] [Updated] (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:all-tabpanel ]

Sebb updated INFRA-6218:
------------------------

    Description: 
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.

  was:
Recently we're extremely suffering from different wired 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 read 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.

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