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

[GitHub] zeppelin pull request #2476: [ZEPPELIN-2579] Flaky Test: InterpreterOutputCh...

GitHub user jongyoul opened a pull request:

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

    [ZEPPELIN-2579] Flaky Test: InterpreterOutputChangeWatcher.test

    ### What is this PR for?
    Fixing flaky test
    ```
    Running org.apache.zeppelin.interpreter.InterpreterOutputChangeWatcherTest
    15:12:09,215  INFO org.apache.zeppelin.interpreter.InterpreterOutputChangeWatcher:71 - watch /tmp/ZeppelinLTest_1498403528213
    15:12:10,223  INFO org.apache.zeppelin.interpreter.InterpreterOutputChangeWatcher:125 - File change detected /tmp/ZeppelinLTest_1498403528213/test1
    15:12:10,224  INFO org.apache.zeppelin.interpreter.InterpreterOutputChangeWatcher:125 - File change detected /tmp/ZeppelinLTest_1498403528213/test1
    Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 32.034 sec <<< FAILURE! - in org.apache.zeppelin.interpreter.InterpreterOutputChangeWatcherTest
    test(org.apache.zeppelin.interpreter.InterpreterOutputChangeWatcherTest)  Time elapsed: 32.031 sec  <<< FAILURE!
    java.lang.AssertionError: expected:<1> but was:<2>
    	at org.junit.Assert.fail(Assert.java:88)
    	at org.junit.Assert.failNotEquals(Assert.java:834)
    	at org.junit.Assert.assertEquals(Assert.java:645)
    	at org.junit.Assert.assertEquals(Assert.java:631)
    	at org.apache.zeppelin.interpreter.InterpreterOutputChangeWatcherTest.test(InterpreterOutputChangeWatcherTest.java:95)
    ```
    
    ### What type of PR is it?
    [Bug Fix]
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    * https://issues.apache.org/jira/browse/ZEPPELIN-2759
    
    ### How should this be tested?
    Pass CI
    
    ### 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/jongyoul/zeppelin ZEPPELIN-2759

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

    https://github.com/apache/zeppelin/pull/2476.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 #2476
    
----
commit b7446ae30ff208c249d0a4eeb4446c18826e13f3
Author: Jongyoul Lee <jo...@gmail.com>
Date:   2017-07-10T16:47:24Z

    Fixed flaky test

----


---
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 #2476: [ZEPPELIN-2579] Flaky Test: InterpreterOutputCh...

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

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


---