Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2511
awesome!
---
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 Sdedelbrock commented on the issue:
https://github.com/apache/zeppelin/pull/2511
it.
finally..
happened!
ð
---
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
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/2511
You can close/open this PR to trigger Jenkins. Then Jenkins will check last
build result and update this PR build status. Or just leaving message would be
okay too, like you just did.
Github user Sdedelbrock commented on the issue:
https://github.com/apache/zeppelin/pull/2511
I've force pushed the PR twice to re-trigger the build, and one of the jobs
consistently times out. I have disabled test concurrency to no avail. I have
manually re-run the (failed) test
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2511
yes, let's get CI to run though :)
---
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
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2511
could you please setup travis CI to run tests
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
---
If your project is set up for it, you can reply to
