On 07/13/2014 04:29 PM, Dipanjan Laha wrote: > Hello, > > I checked in some code yesterday in commons collection. This triggered a > build which failed. The log around the failure reads > > [commons-collections] $ /home/hudson/tools/java/latest1.5/bin/java -cp > /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.3/boot/plexus-classworlds-2.4.jar > org.jvnet.hudson.maven3.agent.Maven3Main > /home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.3 > /home/jenkins/jenkins-slave/slave.jar > /home/jenkins/jenkins-slave/maven3-interceptor.jar > /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 52835 > ERROR: Failed to parse POMsjava.io.IOException > <http://stacktrace.jenkins-ci.org/search?query=java.io.IOException>: > Cannot run program "/home/hudson/tools/java/latest1.5/bin/java" (in > directory "/home/jenkins/jenkins-slave/workspace/commons-collections"): > error=2, No such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041) > <http://stacktrace.jenkins-ci.org/search/?query=java.lang.ProcessBuilder.start&entity=method> > at hudson.Proc$LocalProc.<init>(Proc.java:244) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.Proc$LocalProc.%3Cinit%3E&entity=method> > at hudson.Proc$LocalProc.<init>(Proc.java:216) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.Proc$LocalProc.%3Cinit%3E&entity=method> > at hudson.Launcher$LocalLauncher.launch(Launcher.java:773) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$LocalLauncher.launch&entity=method> > at hudson.Launcher$ProcStarter.start(Launcher.java:353) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$ProcStarter.start&entity=method> > at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:998) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$RemoteLaunchCallable.call&entity=method> > at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:965) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.Launcher$RemoteLaunchCallable.call&entity=method> > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.UserRequest.perform&entity=method> > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.UserRequest.perform&entity=method> > at hudson.remoting.Request$2.run(Request.java:328) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request$2.run&entity=method> > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.InterceptingExecutorService$1.call&entity=method> > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.FutureTask.run&entity=method> > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor.runWorker&entity=method> > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > <http://stacktrace.jenkins-ci.org/search/?query=java.util.concurrent.ThreadPoolExecutor$Worker.run&entity=method> > at java.lang.Thread.run(Thread.java:745) > <http://stacktrace.jenkins-ci.org/search/?query=java.lang.Thread.run&entity=method> > Caused by: java.io.IOException > <http://stacktrace.jenkins-ci.org/search?query=java.io.IOException>: > error=2, No such file or directory > at java.lang.UNIXProcess.forkAndExec(Native Method) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:186) > at java.lang.ProcessImpl.start(ProcessImpl.java:130) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022) > ... 14 more > > > The error seems quite strange as it apparently indicates that java is not > available. I am a newbie here and I am not aware of the build setup and > server. It would be great if someone can help me out with this. In fact, > this was my first commit and I am not sure if I missed something from my > side. The commit revisions are r1610049 and r1610057.
I restarted the build and everything is back to normal. It can happen that builds there fail from time to time due to other issues, so nothing to worry about too much. Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org