lmccay commented on PR #506:
URL: https://github.com/apache/incubator-livy/pull/506#issuecomment-3761059850

   > @lmccay Also
   > 
   > the errors:
   > 
   > at 
org.apache.livy.thriftserver.LivyThriftSessionManager.$anonfun$openSession$2(LivyThriftSessionManager.scala:269)
 at scala.concurrent.Future$.$anonfun$apply$1(Future.scala:659) ... Cause: 
java.io.IOException: RSCClient instance stopped. at 
org.apache.livy.rsc.RSCClient.stop(RSCClient.java:245) at 
org.apache.livy.rsc.RSCClient.connectionError(RSCClient.java:155) at 
org.apache.livy.rsc.RSCClient.access$300(RSCClient.java:51) at 
org.apache.livy.rsc.RSCClient$1.onFailure(RSCClient.java:95) at 
org.apache.livy.rsc.Utils$2.operationComplete(Utils.java:108) at 
io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590)
 at 
io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:583)
 at 
io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:559)
 at io.netty.util.concurrent.DefaultPromise.access$200(DefaultPromise.java:35) 
at io.netty.util.concurrent.DefaultPromise$1.run(DefaultPromise.java:503)
   > 
   > I think this entire suite is flakey, Just my opinion but they fail 
sometimes when i run master. They fail randomly quite often.
   
   We should revisit those then. If there is no JIRA then go ahead and file one 
and target 0.10.0 release. NOTE: if we drop java 8 altogether at that time, it 
may be a 1.0.0.
   
   There are plenty of PRs that aren't failing these, so trying a rerun should 
get a pass at some point.
   I've rerun a couple on your PRs, not sure if it includes this one, and they 
were still failing.
   
   I'm going to be out of pocket for a bit - maybe will make it back later this 
evening but heading out now.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to