Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1240
Looks great to me!
Thank you @prasadwagle for taking care.
Merging to master, if there is no further discussion.
---
If your project is set up for it, you can reply to this email an
Github user prasadwagle commented on the issue:
https://github.com/apache/zeppelin/pull/1240
@Leemoonsoo @bzz @jongyoul The build is finally green! Is it ok to merge
this change?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1240
@prasadwagle Thanks for fighting the CI. We're also struggling against CI
flaky or failed tests
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user prasadwagle commented on the issue:
https://github.com/apache/zeppelin/pull/1240
I got the latest master with #1261 Two checks in the last build failed. I
am going to close and reopen PR to restart build.
https://travis-ci.org/apache/zeppelin/jobs/149535134
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1240
That error is handling with #1261
---
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
enable
Github user prasadwagle commented on the issue:
https://github.com/apache/zeppelin/pull/1240
Latest build failing with:
---
T E S T S
---
Running org.apache.zeppelin.
Github user prasadwagle commented on the issue:
https://github.com/apache/zeppelin/pull/1240
I rebased my branch of latest master and pushed it to origin, closed and
reopened pull request but the travis build hasn't started. What is the reason
for that?
```
tw-172-25-130-
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1240
Could you please rebase it? it would be fixed yesterday.
---
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 h