I'm pretty convinced this was an environmental issue -- things seem well enough on some our internal builds of apache branches.
Jon. On Tue, Sep 4, 2012 at 7:56 PM, Stack <[email protected]> wrote: > On Tue, Sep 4, 2012 at 7:07 PM, Jonathan Hsieh <[email protected]> wrote: > > It seems like a lot of the recent hbase apache jenkins builds have been > > failing with this message: > > > > > > FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: > > Unexpected termination of the > > channelhudson.remoting.RequestAbortedException > > < > http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException > >: > > hudson.remoting.RequestAbortedException: java.io.IOException: > > Unexpected termination of the channel > > at hudson.remoting.Request.call(Request.java:174) > > < > http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request.call&entity=method > > > > at hudson.remoting.Channel.call(Channel.java:663) > > < > http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.call&entity=method > > > > at > hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) > > < > http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.RemoteInvocationHandler.invoke&entity=method > > > > at $Proxy38.join(Unknown Source) > > > > > > This says it may be due to environmental issues. > > > http://stackoverflow.com/questions/9998298/jenkins-slave-jobs-failing-on-unexpected-termination-of-channel > > > Thanks Jon. > St.Ack > -- // Jonathan Hsieh (shay) // Software Engineer, Cloudera // [email protected]
