[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user vipul1409 commented on the issue: https://github.com/apache/zeppelin/pull/2090 @felixcheung My user id is vipul.1...@gmail.com --- 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] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2090 merged to master and branch-0.7 --- 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] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2090 @vipul1409 do you have a user ID in Apache JIRA? We could resolve this issue to you. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2090 merging if no more comment --- 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] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2090 it looks like it passed with this build https://travis-ci.org/vipul1409/zeppelin/builds/207896434 --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user vipul1409 commented on the issue: https://github.com/apache/zeppelin/pull/2090 Can this PR be 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 feature enabled and

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user vipul1409 commented on the issue: https://github.com/apache/zeppelin/pull/2090 There is not SparkRInterpreterTest.java, looks like there are no test for SparkR. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2090 Do we have unit tests for SparkR? If so it would be good to add a test for this. Otherwise looks good to me --- If your project is set up for it, you can reply to this email and have

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/2090 @Leemoonsoo Travis CI everything passes actually - it looks like Jenkins has timed-out while the last suite was still running. --- If your project is set up for it, you can reply to

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user vipul1409 commented on the issue: https://github.com/apache/zeppelin/pull/2090 Re ran the failed job and it 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

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user vipul1409 commented on the issue: https://github.com/apache/zeppelin/pull/2090 Thanks for your help @prabhjyotsingh . I can see the build started in travis now. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/2090 I still don't see any builds on your travis (https://travis-ci.org/vipul1409/zeppelin/branches). Can you do a empty commit on this branch (ZEPPELIN-2199) `git commit --amend;git

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user vipul1409 commented on the issue: https://github.com/apache/zeppelin/pull/2090 I have enabled travis for my fork. At this URL https://travis-ci.org/vipul1409/zeppelin/settings "Build pushes" and "Build pull requests" are enabled. is there any other setting that needs to

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/2090 I meant https://travis-ci.org/vipul1409/zeppelin/settings instead of "andreaTP". Typo --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user prabhjyotsingh commented on the issue: https://github.com/apache/zeppelin/pull/2090 Did you switch on 'zeppelin' repository from https://travis-ci.org/profile (https://zeppelin.apache.org/contribution/contributions.html#continuous-integration) ? Also after

[GitHub] zeppelin issue #2090: ZEPPELIN-2199: Fix lapply issue in sparkR

Github user vipul1409 commented on the issue: https://github.com/apache/zeppelin/pull/2090 Can anyone help me understand the build error it looks unrelated to my change, --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.