www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Munteanu (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 Wed, 10 Jul 2013 08:03:49 GMT

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

Robert Munteanu commented on INFRA-6218:

I've attached a zip file containing the full build logs of the most recent 5 failed sling-trunk-1.6
builds. What I can make out of it is:

- the submodule failing varies - there are 3 submodules failing
- the slave varies as well, but recently it has only failed on ubuntu5

Let me know if there's any more information that I can give you or help in any other way.

$ grep -ae '\. FAILURE' *

sling-trunk-1.6-1684.txt:[INFO] Apache Sling JCR Resource Resolver ................ FAILURE
sling-trunk-1.6-1723.txt:[INFO] Apache Sling Event Support ........................ FAILURE
sling-trunk-1.6-1728.txt:[INFO] Apache Sling Event Support ........................ FAILURE
sling-trunk-1.6-1729.txt:[INFO] Apache Sling JCR Resource Resolver ................ FAILURE
sling-trunk-1.6-1730.txt:[INFO] Apache Sling Event Support ........................ FAILURE

$ grep -ae 'Building remotely' *
sling-trunk-1.6-1684.txt:Building remotely on ubuntu6 in workspace /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6
sling-trunk-1.6-1723.txt:Building remotely on ubuntu5 in workspace /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6
sling-trunk-1.6-1728.txt:Building remotely on ubuntu5 in workspace /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6
sling-trunk-1.6-1729.txt:Building remotely on ubuntu5 in workspace /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6
sling-trunk-1.6-1730.txt:Building remotely on ubuntu5 in workspace /home/jenkins/jenkins-slave/workspace/sling-trunk-1.6

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

View raw message