Yes, unfortunately new jobs will have the option of the slave or the master. The slave doesn't have currently have access to the eclipse.org filesystem so it's not ideal for running builds :-) Right now, I'm just testing it.
Kim David Carver <d_a_car...@yahoo.com> Sent by: dash-dev-boun...@eclipse.org 12/05/2009 03:40 PM Please respond to Tools for Committer Community <dash-dev@eclipse.org> To Tools for Committer Community <dash-dev@eclipse.org> cc Subject Re: [dash-dev] Weird failure.. Okay, tying it to the Hudson Master node seems to have fixed the issue. Dave Miles Parker wrote: > No, it's been running for a few months now. It's just the default setup. Still failing as of 8 am this monring. > > On Dec 5, 2009, at 7:02 AM, David Carver wrote: > > >> Is this a new job. If so it looks like it is trying to run on the test-slave machine, instead of the Master. In your job configuration, make sure you tell it to only run on the Master machine, and not the slave machine. >> >> Dave >> >> Miles Parker wrote: >> >>> I'm getting an awfully strange issue..nothing significant (if >>> anything) changed since the last time everything built... >>> >>> https://build.eclipse.org/hudson/job/cbi-amp-nightly/ >>> >>> Any ideas? >>> >>> A SCM change trigger started this job >>> Building remotely on test-slave >>> FATAL: Cannot run program "cvs" (in directory >>> "/home/hudsonbuild/slave_jobs/workspace/cbi-amp-nightly"): >>> java.io.IOException: error=2, No such file or directory >>> java.io.IOException: Cannot run program "cvs" (in directory >>> "/home/hudsonbuild/slave_jobs/workspace/cbi-amp-nightly"): >>> java.io.IOException: error=2, No such file or directory >>> at java.lang.ProcessBuilder.start(ProcessBuilder.java:474) >>> at hudson.Proc$LocalProc.<init>(Proc.java:145) >>> at hudson.Proc$LocalProc.<init>(Proc.java:118) >>> at hudson.Launcher$LocalLauncher.launch(Launcher.java:633) >>> at hudson.Launcher$ProcStarter.start(Launcher.java:268) >>> at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:773) >>> at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:751) >>> at hudson.remoting.UserRequest.perform(UserRequest.java:103) >>> at hudson.remoting.UserRequest.perform(UserRequest.java:47) >>> at hudson.remoting.Request$2.run(Request.java:236) >>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >>> 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:1110) >>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) >>> at java.lang.Thread.run(Thread.java:636) >>> Caused by: java.io.IOException: java.io.IOException: error=2, No such >>> file or directory >>> at java.lang.UNIXProcess.<init>(UNIXProcess.java:164) >>> at java.lang.ProcessImpl.start(ProcessImpl.java:81) >>> at java.lang.ProcessBuilder.start(ProcessBuilder.java:467) >>> ... 15 more >>> _______________________________________________ >>> dash-dev mailing list >>> dash-dev@eclipse.org >>> https://dev.eclipse.org/mailman/listinfo/dash-dev >>> >>> >>> >> _______________________________________________ >> dash-dev mailing list >> dash-dev@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/dash-dev >> > > _______________________________________________ > dash-dev mailing list > dash-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/dash-dev > > _______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
