Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/1094
Yes, I've seen this, this happens when spark takes longer that 60sec to
start up.
Will open up a new jira and fix this as well.
---
If your project is set up for it, you can reply to
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1094
CI failure is not related and handled under
[ZEPPELIN-1073](https://issues.apache.org/jira/browse/ZEPPELIN-1073)
Merging if there is no further disucssion
---
If your project is set up for it, yo
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1094
CI fails on Integration tests, and failure looks different from #1091 and
#1092
```
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 143.455 sec
- in org.apache.zeppelin.i
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1094
Rebased on latest master, after #1092 got merged
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feat
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1094
Ready to be merged, \cc @minahlee @prabhjyotsingh for review.
CI failure is being taken care of under #1092
---
If your project is set up for it, you can reply to this email and have your
re
