thank you Olivier let's hope this will improve the situation
Regards, Hervé Le vendredi 13 décembre 2013 17:00:41 Olivier Lamy a écrit : > upgraded to jdk1.7.0_25 > https://builds.apache.org/computer/ubuntu1/systemInfo > > except ubuntu2/5 which cannot be reach. > > On 13 December 2013 04:59, Robert Munteanu <[email protected]> wrote: > > On Thu, Dec 12, 2013 at 7:55 PM, Hervé BOUTEMY <[email protected]> wrote: > >> the build is launched in a different Unix process than the slave, with a > >> different JDK > >> > >> my idea (based on nothing other than pure speculation, since I have no > >> evidence) is to change the JDK used by Jenkins slave itself > >> see https://builds.apache.org/computer/ubuntu1/systemInfo > >> > >> I really don't have any precise idea why Ubuntu slaves are all fragile > >> these days, where windows slaves run pretty well > >> OS taken apart, the main difference I see is OpenJDK 1.6 on Ubuntu slaves > >> and Oracle JDK 7 on Windows slaves > > > > Ah, I see. I second your idea then, since OpenJDK 6 is in my > > experience not on par with Oracle's JDK 6, whereas OpenJDK 7 is much > > better. > > > > I've added this to https://issues.apache.org/jira/browse/INFRA-6218 , > > so it does not get lost. > > > > Robert > > > >> Regards, > >> > >> Hervé > >> > >> Le jeudi 12 décembre 2013 10:50:01 Robert Munteanu a écrit : > >>> On Wed, Dec 11, 2013 at 7:09 PM, Hervé BOUTEMY <[email protected]> > >> > >> wrote: > >>> > I see Ubuntu slaves run OpenJDK 1.6 > >>> > maybe upgrading to OpenJDK 7 may improve things? > >>> > >>> In the Sling project we're seeing build failures with OpenJDK 7 as well. > >>> > >>> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/ > >>> > >>> Robert > >>> > >>> > Regards, > >>> > > >>> > Hervé > >>> > > >>> > Le mercredi 11 décembre 2013 14:28:39 Hervé BOUTEMY a écrit : > >>> >> 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-stri > >>> >> pes- > >>> >> 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-stri > >>> >> pes- > >>> >> 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(RemoteInvo > >>> >> cati > >>> >> onH andler.java:293) at > >>> >> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocat > >>> >> ionH > >>> >> and ler.java:280) at > >>> >> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocat > >>> >> ionH > >>> >> and ler.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(InterceptingExecut > >>> >> orSe > >>> >> rvi ce.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 > >>> >> > >>> >> :11 45) at > >>> >> > >>> >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor > >>> >> .jav > >>> >> a:6 15) 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 > > > > -- > > Sent from my (old) computer
