Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2041
ah, yes, I didn't realize this is based of branch-0.7 - we should create PR
off master instead.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2041
@samthebest could you rebase this PR to get it to run CI tests?
---
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/2041
The change 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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2041
Yes, Jenkins couldn't run 'travis_check.py' because of this PR is based on
folk before 'travis_check.py' exists.
---
If your project is set up for it, you can reply to this email and have
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2041
Hmm ok :)
it looks like there's an issue with the Jenkins check
```
[zeppelin-pull-request] $ /bin/bash -xe /tmp/hudson1411217650836319294.sh
+ '[' -f travis_check.py ']'
+
