sveryovka commented on PR #4497:
URL: https://github.com/apache/zeppelin/pull/4497#issuecomment-1298805443

   @Reamer in the last build of this branch following test are failing
   zeppelin-integration-test
   spark-integration-test (2,11)
   spark-integration-test (3,11)
   spark-test (3.7, 11)
   
   For zeppelin-integration-test
   here 
https://github.com/apache/zeppelin/actions/runs/3368725277/jobs/5587598713
   you have 3 tst failuers
   Error:  Errors: 
   Error:    ZSessionIntegrationTest.testZSession_Flink:331 »  Fail to init 
session, org.ap...
   Error:    ZSessionIntegrationTest.testZSession_Flink_Submit:368 »  Fail to 
init session,...
   Error:    ZSessionIntegrationTest.testZSession_Spark_Submit:315 »  Unable to 
call rest a...
   
   During our work we had a source code state at which 
   for Java 8 https://github.com/sveryovka/zeppelin/actions/runs/3172401737 it 
was all ok (livy was failing since fix was not yet merged so this is expected)
   for Java 11 https://github.com/sveryovka/zeppelin/actions/runs/3172401749 
zeppelin-integration-test was passing successfully
   
   Unfortunately it is not possible to simply take some commit in this case. 
Since our branch was not synced yet with the upstream. I guess we may take 
corresponding commit, compare differences with code in this PR and try some 
things. It will not be easy since there will be a lot of differences because 
upstream and our branch was evolving separately for some time. I may try to 
look at this but because of personal issues it may not happen soon. So if you 
have time and you think that it worth investigating you are welcome to check 
this as well. If you do not have time right now I may look at this later.
    


-- 
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: dev-unsubscr...@zeppelin.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to