I took a quick look and didn't see any additional info. In my experience, we're IO and similar errors typically mean that something is not good with the host. Internally, the way I usually solve this if it's not a one-time transient thing is to simply exclude the job from running on that host. In this case, it seems to be different hosts each time, and one host that worked and didn't work; so I'm not sure that's the right solution here.
On Mon, May 5, 2014 at 12:20 PM, Rohini Palaniswamy <[email protected] > wrote: > https://builds.apache.org/job/oozie-trunk-precommit-build/ - 4 builds > starting from Build #1210 (May 2, 2014 2:11:55 PM), builds have got > terminated when running tests with > > FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: > Unexpected termination of the channel > hudson.remoting.RequestAbortedException: > hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected > termination of the channel > at > > hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) > at > > hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) > at hudson.remoting.Request.call(Request.java:174) > at hudson.remoting.Channel.call(Channel.java:739) > at > > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) > > Doesn't look like it was manually aborted. Can someone with more access > check if some info shows up as to the cause? If not we will have to file an > INFRA jira. > > - Rohini >
