Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 393083

Summary: Cannot run program "pkill" on mac-tests2, occasionally.
Product: Community Reporter: David Williams <david_williams>
Component: CI-JenkinsAssignee: CI Admin Inbox <ci.admin-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: P3 CC: webmaster
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description David Williams CLA 2012-10-29 14:04:22 EDT
First noted this odd behavior in bug 340991. And it still happens, where once or twice a week our automated unit test job fails right away complaining it can not find "pkill" ... which should be "built-in"?! 

Such as see 
https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/ep4-unit-mac64/84/console


Marking as "minor" since easy to work around ... I just restart the job manually, and it works ok that next time. 

Not sure what could cause this ... disk being "spun-down" for power saving and not yet spun-up when the job starts? ... but thought it deserved documenting here in case its a known issue or gets worse. 

It would be worse for us if I wasn't sent a text message each time our job fails :) so I can re-start it right away. [just because of how I've set up our code, its not part of hudson]. It would have more impact if it wasn't noticed for hours and hours and then the test would be "late". 

= = = = = 

Started by user anonymous
Building remotely on mac-tests2
Cleaning the workspace because project is configured to clean the workspace before each build.
$ pkill Xvnc
FATAL: Cannot run program "pkill": error=2, No such file or directory
java.io.IOException: Cannot run program "pkill": error=2, No such file or directory
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
	at hudson.Proc$LocalProc.<init>(Proc.java:192)
	at hudson.Proc$LocalProc.<init>(Proc.java:164)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:639)
	at hudson.Launcher$ProcStarter.start(Launcher.java:274)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:794)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:768)
	at hudson.remoting.UserRequest.perform(UserRequest.java:114)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:283)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:680)
Caused by: java.io.IOException: error=2, No such file or directory
	at java.lang.UNIXProcess.forkAndExec(Native Method)
	at java.lang.UNIXProcess.<init>(UNIXProcess.java:53)
	at java.lang.ProcessImpl.start(ProcessImpl.java:91)
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:453)
	... 15 more
Comment 1 Eclipse Webmaster CLA 2012-10-31 11:47:39 EDT
Looks like the path wasn't being picked up from .bashrc.  I've moved it into .profile and now it seems better(at least on the command line).

BTW pkill isn't a 'native' OSX tool, it needs to be installed.

-M.
Comment 2 David Williams CLA 2012-11-06 01:01:53 EST
(In reply to comment #1)
> Looks like the path wasn't being picked up from .bashrc.  I've moved it into
> .profile and now it seems better(at least on the command line).
> 
> BTW pkill isn't a 'native' OSX tool, it needs to be installed.
> 
> -M.

Thanks for letting me know its not "native" ... always something new to learn. 

But, the problem happened again here on November 6th. 
https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/ep4-unit-mac64/93/console

(I'm not too worried about it ... just keeping track).
Comment 3 David Williams CLA 2012-11-06 01:08:29 EST
(In reply to comment #2)
> (In reply to comment #1)

> 
> (I'm not too worried about it ... just keeping track).

But, am worried about bug 393625 ... perhaps the changes made here effected "wget"?