[ZEPPELIN-1063] Flaky Test - PythonInterpreterTest.testClose

• Type: Test
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.6.0
• Fix Version/s: 0.7.0
• Component/s: python-interpreter
• Labels: flaky-test
• Assignee: Alexander Bezzubov
• Reporter: Mina Lee
• Created: 26/Jun/16 06:49
• Updated: 07/Jul/16 03:47
• Resolved: 07/Jul/16 03:47

Description

Happens on CI environment:

• in https://github.com/apache/zeppelin/pull/1091 - logs
• on master - logs
• on https://github.com/apache/zeppelin/pull/1100 - logs

Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.486 sec <<< FAILURE! - in org.apache.zeppelin.python.PythonInterpreterTest
testClose(org.apache.zeppelin.python.PythonInterpreterTest)  Time elapsed: 0.377 sec  <<< FAILURE!
java.lang.AssertionError: null
    at org.junit.Assert.fail(Assert.java:86)
    at org.junit.Assert.assertTrue(Assert.java:41)
    at org.junit.Assert.assertFalse(Assert.java:64)
    at org.junit.Assert.assertFalse(Assert.java:74)
    at org.apache.zeppelin.python.PythonInterpreterTest.testClose(PythonInterpreterTest.java:141)

Which, from the code

    //when
    pythonInterpreter.close();
    //then
    assertFalse(serverIsListeningOn(py4jPort));

means that after interpreter has been .close() - there is still a process, listening on py4jPort.

Issue Links

• links to: GitHub Pull Request #1094
• links to: GitHub Pull Request #1123
• links to: GitHub Pull Request #1134