[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/1896 ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
GitHub user cloverhearts reopened a pull request: https://github.com/apache/zeppelin/pull/1896 implementation test case for connect to exists interpreter process ### What is this PR for? We need test case for remote interpreter process ( connect to exists process) ### What type of PR is it? [TEST case] ### What is the Jira issue? none (jira problem now) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloverhearts/zeppelin remoteInterpreterTEST Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1896.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1896 commit 87a5613f87b8e0e933be87a887da0206a4c6e15f Author: cloverheartsDate: 2017-01-13T02:14:40Z Implement test case for remote interpreter connect to exists process commit 9d54daaea0bc3c1f771c01347c592fad13e1ac13 Author: cloverhearts Date: 2017-01-16T06:30:06Z Merge branch 'master' into remoteInterpreterTEST commit 1edbd1eaa9f578b6327007fe907af8885504ae16 Author: cloverhearts Date: 2017-01-16T06:35:20Z Instance of RemoteInterpreter to mock --- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
Github user cloverhearts closed the pull request at: https://github.com/apache/zeppelin/pull/1896 --- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
Github user cloverhearts closed the pull request at: https://github.com/apache/zeppelin/pull/1896 --- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
GitHub user cloverhearts reopened a pull request: https://github.com/apache/zeppelin/pull/1896 implementation test case for connect to exists interpreter process ### What is this PR for? We need test case for remote interpreter process ( connect to exists process) ### What type of PR is it? [TEST case] ### What is the Jira issue? none (jira problem now) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloverhearts/zeppelin remoteInterpreterTEST Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1896.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1896 commit 87a5613f87b8e0e933be87a887da0206a4c6e15f Author: cloverheartsDate: 2017-01-13T02:14:40Z Implement test case for remote interpreter connect to exists process --- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
Github user cloverhearts closed the pull request at: https://github.com/apache/zeppelin/pull/1896 --- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
GitHub user cloverhearts reopened a pull request: https://github.com/apache/zeppelin/pull/1896 implementation test case for connect to exists interpreter process ### What is this PR for? We need test case for remote interpreter process ( connect to exists process) ### What type of PR is it? [TEST case] ### What is the Jira issue? none (jira problem now) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloverhearts/zeppelin remoteInterpreterTEST Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1896.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1896 commit 87a5613f87b8e0e933be87a887da0206a4c6e15f Author: cloverheartsDate: 2017-01-13T02:14:40Z Implement test case for remote interpreter connect to exists process --- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
Github user cloverhearts closed the pull request at: https://github.com/apache/zeppelin/pull/1896 --- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] zeppelin pull request #1896: implementation test case for connect to exists ...
GitHub user cloverhearts opened a pull request: https://github.com/apache/zeppelin/pull/1896 implementation test case for connect to exists interpreter process ### What is this PR for? We need test case for remote interpreter process ( connect to exists process) ### What type of PR is it? [TEST case] ### What is the Jira issue? none (jira problem now) ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/cloverhearts/zeppelin remoteInterpreterTEST Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/1896.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1896 commit 87a5613f87b8e0e933be87a887da0206a4c6e15f Author: cloverheartsDate: 2017-01-13T02:14:40Z Implement test case for remote interpreter connect to exists process --- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---