[GitHub] zeppelin pull request #2874: ZEPPELIN-3339. Add more test for ZeppelinContex...

[zjffdu <gi...@git.apache.org>]

GitHub user zjffdu opened a pull request:

    https://github.com/apache/zeppelin/pull/2874

    ZEPPELIN-3339. Add more test for ZeppelinContext

    ### What is this PR for?
    
    Add more test for ZeppelinContext, especially for run api and ResourcePool
    
    
    ### What type of PR is it?
    [Improvement  | Refactoring]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-3339
    
    ### How should this be tested?
    * CI pass
    
    ### Screenshots (if appropriate)
    
    ### 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/zjffdu/zeppelin ZEPPELIN-3339

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/zeppelin/pull/2874.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 #2874
    
----
commit 83de188239123b8866ca38d0e46ad843de8f62da
Author: Jeff Zhang <zj...@...>
Date:   2018-03-15T08:04:57Z

    ZEPPELIN-3339. Add more test for ZeppelinContext

----


---

[GitHub] zeppelin issue #2874: ZEPPELIN-3339. Add more test for ZeppelinContext

[felixcheung <gi...@git.apache.org>]

Github user felixcheung commented on the issue:

    https://github.com/apache/zeppelin/pull/2874
  
    hey @zjffdu thanks for making all these improvements, could we make sure there is at least one review before merging?
    @Leemoonsoo 


---

[GitHub] zeppelin pull request #2874: ZEPPELIN-3339. Add more test for ZeppelinContex...

[asfgit <gi...@git.apache.org>]

Github user asfgit closed the pull request at:

    https://github.com/apache/zeppelin/pull/2874


---