You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by Leemoonsoo <gi...@git.apache.org> on 2017/02/15 15:26:58 UTC

[GitHub] zeppelin pull request #2022: [ZEPPELIN-2120] Flaky Test: NotebookTest.testRu...

GitHub user Leemoonsoo opened a pull request:

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

    [ZEPPELIN-2120] Flaky Test: NotebookTest.testRunAll

    ### What is this PR for?
    Fix Flaky test NotebookTest.testRunAll
    
    ### What type of PR is it?
    Bug Fix
    
    ### Todos
    * [x] - Fix flaky test
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-2120
    
    ### How should this be tested?
    check ci becomes green
    
    ### 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/Leemoonsoo/zeppelin ZEPPELIN-2120

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

    https://github.com/apache/zeppelin/pull/2022.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 #2022
    
----
commit 008ec4a831947f00bf8539caab5154861ea42958
Author: Lee moon soo <mo...@apache.org>
Date:   2017-02-15T15:25:01Z

    wait while result is null

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2022: [ZEPPELIN-2120] Flaky Test: NotebookTest.testRunAll

Posted by AhyoungRyu <gi...@git.apache.org>.
Github user AhyoungRyu commented on the issue:

    https://github.com/apache/zeppelin/pull/2022
  
    CI is all green now. I think it's GOOT TO GO \U0001f3c3\U0001f3fb


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2022: [ZEPPELIN-2120] Flaky Test: NotebookTest.testRu...

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2022: [ZEPPELIN-2120] Flaky Test: NotebookTest.testRu...

Posted by Leemoonsoo <gi...@git.apache.org>.
GitHub user Leemoonsoo reopened a pull request:

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

    [ZEPPELIN-2120] Flaky Test: NotebookTest.testRunAll

    ### What is this PR for?
    Fix Flaky test NotebookTest.testRunAll
    
    ### What type of PR is it?
    Bug Fix
    
    ### Todos
    * [x] - Fix flaky test
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-2120
    
    ### How should this be tested?
    check ci becomes green
    
    ### 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/Leemoonsoo/zeppelin ZEPPELIN-2120

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

    https://github.com/apache/zeppelin/pull/2022.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 #2022
    
----
commit 7ee7febc61f8d672d4df82449044bb55696a5269
Author: Lee moon soo <mo...@apache.org>
Date:   2017-02-15T15:25:01Z

    wait while result is null

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2022: [ZEPPELIN-2120] Flaky Test: NotebookTest.testRunAll

Posted by Leemoonsoo <gi...@git.apache.org>.
Github user Leemoonsoo commented on the issue:

    https://github.com/apache/zeppelin/pull/2022
  
    Thanks @AhyoungRyu for review.
    Merge to master if no more comments.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2022: [ZEPPELIN-2120] Flaky Test: NotebookTest.testRunAll

Posted by qinchaofeng <gi...@git.apache.org>.
Github user qinchaofeng commented on the issue:

    https://github.com/apache/zeppelin/pull/2022
  
    cool


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2022: [ZEPPELIN-2120] Flaky Test: NotebookTest.testRu...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

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


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---