seems like we already have stuck builds for strange causes: ubuntu6 https://builds.apache.org/job/Tuscany-2x/1212/console [INFO] [install:install {execution: default-install}] [INFO] Installing /home/jenkins/jenkins- slave/workspace/Tuscany-2x/sca-2x/modules/stripes/target/tuscany-stripes-2.5- SNAPSHOT.jar to /home/jenkins/jenkins- slave/workspace/Tuscany-2x/.repository/org/apache/tuscany/sca/tuscany- stripes/2.5-SNAPSHOT/tuscany-stripes-2.5-SNAPSHOT.jar [INFO] Installing /home/jenkins/jenkins- slave/workspace/Tuscany-2x/sca-2x/modules/stripes/target/tuscany-stripes-2.5- SNAPSHOT-sources.jar to /home/jenkins/jenkins- slave/workspace/Tuscany-2x/.repository/org/apache/tuscany/sca/tuscany- stripes/2.5-SNAPSHOT/tuscany-stripes-2.5-SNAPSHOT-sources.jar [JENKINS] Archiving disabled Build timed out (after 200 minutes). Marking the build as aborted. [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Unable to call setResult. Invalid object ID 20 [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.IllegalStateException: Unable to call setResult. Invalid object ID 20 at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:293) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) [INFO] ------------------------------------------------------------------------ [INFO] Total time: 196 minutes 40 seconds [INFO] Finished at: Wed Dec 11 11:21:18 UTC 2013 [INFO] Final Memory: 157M/973M [INFO] ------------------------------------------------------------------------
same on ubuntu1 with Camel.trunk.fulltest [ERROR] Internal error: java.lang.IllegalStateException: Unable to call isArchivingDisabled. Invalid object ID 207 -> [Help 1] any idea, why: 1. this is failing? 2. it is hanging? would something like Timestamper plugin https://wiki.jenkins-ci.org/display/JENKINS/Timestamper help us discover where hanging happens? Any other idea? Regards, Hervé Le mardi 10 décembre 2013 17:27:43 Gavin McDonald a écrit : > > -----Original Message----- > > From: larry mccay [mailto:[email protected]] > > Sent: Tuesday, 10 December 2013 11:24 AM > > To: [email protected] > > Subject: Jenkins Ubuntu Health? > > > > Greetings - > > > > I manually kicked off a build for our Knox 0.3.1 release branch/candidate > > today and it has been pending awaiting an ubuntu machine all day. > > > > https://builds.apache.org/job/Knox-0.3.1/ > > > > Browsing the various ubuntu machines, it seems that perhaps they are not > > exactly healthy. > > > > Is there an appropriate channel, email list or jira to file in order to > > get the > > > general health checked out? > > you are here > > I've rebooted all Ubuntu slaves. Two haven't returned and are being > investigated (at Y!) > > The rest are back. > > Gav... > > > Thanks in advance, > > > > --larry
