Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2056
merged to master
---
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 feature
enabled and wishes
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2056
ping @felixcheung CI is passed
---
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 feature
enabled
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2056
one failure: https://travis-ci.org/zjffdu/zeppelin/jobs/204447551
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2056
Even though test is not directly related to this PR
I have experienced some code change or additional test may break other
test, because of resource consumption or other unexpected reason.
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/2056
I also think those tests not related to this PR and can be handled in that
separate issue, probably some resource note name was changed
---
If your project is set up for it, you can reply
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2056
CI continue fail in the same place. But this is not livy relevant, as I
didn't change any code outside livy interpreter. I have created ticket
ZEPPELIN-2155 for this
```
Failed
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2056
LGTM!
---
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 feature
enabled and wishes so, or
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2056
looks good, hmm, but the livy 0.3 test is failing
https://travis-ci.org/zjffdu/zeppelin/builds/204166190
and you are saying it's not related to this? shall we kick it off one more
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2056
@felixcheung @prabhjyotsingh Please help review. CI failure is not relevant.
```
Failed tests:
NotebookTest.testPublicPrivateNewNote:1173 expected:<2C[A7GB62Y]> but
