Community
Participate
Working Groups
While investigating bug 488350 (which might be related to DNS failures?) I thought I would take a look at the Hudson "mactest2" logs. I didn't see anything about "DNS failures", but did notice two other issues. - The "time" of that machine is "ahead" of the master Hudson by 8 seconds. I have no idea if that affects our tests .. but, I would guess it would effect Hudson if nothing else. - There a number of errors in the log about "failure of Native Mac Processes". These started a while ago, on 2/10 ... as indicated by this exception, and then .... = = = = = [2016-02-10 05:01:05] Feb 10, 2016 5:01:10 PM org.hudsonci.utils.tasks.Chmod process SEVERE: Failed to chmod: /shared/common/apache-maven-latest/bin/mvn [2016-02-10 05:52:00] Feb 10, 2016 5:52:04 PM org.eclipse.hudson.jna.NativeUtils <init> INFO: Error getting Native Support Extensions java.lang.NullPointerException at org.eclipse.hudson.jna.NativeUnixSupport.all(NativeUnixSupport.java:46) at org.eclipse.hudson.jna.NativeUtils.getAvailableNativeUnixSupports(NativeUtils.java:74) at org.eclipse.hudson.jna.NativeUtils.<init>(NativeUtils.java:48) at org.eclipse.hudson.jna.NativeUtils.getInstance(NativeUtils.java:135) at hudson.util.ProcessTree.get(ProcessTree.java:325) at hudson.Proc$LocalProc.destroy(Proc.java:284) at hudson.Proc$LocalProc.join(Proc.java:257) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:828) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:797) at hudson.remoting.UserRequest.perform(UserRequest.java:107) at hudson.remoting.UserRequest.perform(UserRequest.java:41) at hudson.remoting.Request$2.run(Request.java:276) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) 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:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:695) Feb 10, 2016 5:52:04 PM hudson.util.ProcessTree$Darwin <init> WARNING: Failed to fecth Native Mac Processes [2016-02-10 05:52:00] Feb 10, 2016 5:52:04 PM hudson.util.ProcessTree killAll = = = = = = = and then since 2/10 have been many "Warnings" related to Native Mac Processes. = = = = = = = WARNING: Failed to fecth Native Mac Processes [2016-02-27 01:44:59] Feb 27, 2016 1:45:06 AM hudson.util.ProcessTree killAll INFO: killAll (process started by build): process=java.lang.UNIXProcess@d2324b8 and envs={HUDSON_COOKIE=2c70d51d-dc58-4e41-91f7-de79e992eef0} [2016-02-27 08:44:50] Feb 27, 2016 8:44:58 PM hudson.util.ProcessTree$Darwin <init> WARNING: Failed to fecth Native Mac Processes [2016-02-27 08:44:50] Feb 27, 2016 8:44:58 PM hudson.util.ProcessTree killAll INFO: killAll (process started by build): process=java.lang.UNIXProcess@60bb18e8 and envs={HUDSON_COOKIE=4fdcf99b-2870-4434-a4d0-cdcd4501638a} = = = = = = = = They all are no associated with time we would be testing, but some are.
Oh, and BTW, the Windows machine time is behind by 11 seconds, as indicated at https://hudson.eclipse.org/shared/computer/ Again, no idea if this impacts our build-tests, but intuitively seems it should be closer, since Hudson probably? depends on "time of events" to do its management?
NTP is configured on both of those slaves and seems to be running. Just for grins I manually forced a time update so they should now be in sync. -M.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Closing.
