GitHub user bzz opened a pull request:
https://github.com/apache/zeppelin/pull/1094
ZEPPELIN-1063: fix flaky python interpreter test
### What is this PR for?
fix flaky python interpreter test
### What type of PR is it?
Bug Fix
### Todos
* [ ] cleanup test code
* [ ] fix flaky open port check
### What is the Jira issue?
[ZEPPELIN-1063](https://issues.apache.org/jira/browse/ZEPPELIN-1063)
### How should this be tested?
`mvn "-Dtest=org.apache.zeppelin.python.PythonInterpreterTest" test -pl
python`
### 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/bzz/incubator-zeppelin
fix/python-tests/ZEPPELIN-1063
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1094.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 #1094
----
commit becaa93c805bd4bff148174fb32bc4630864afce
Author: Alexander Bezzubov <[email protected]>
Date: 2016-06-27T10:55:19Z
Python: normalize newlines in tests
commit 37fd4e36f588746ccb0fc39eb5c729a2b67bb97d
Author: Alexander Bezzubov <[email protected]>
Date: 2016-06-27T10:57:39Z
Python: refactoring loggers
commit 815daa7bd1756e7d5049e42ea12011e53498eb48
Author: Alexander Bezzubov <[email protected]>
Date: 2016-06-27T11:03:06Z
Python: refactoring mock() structure and JavaDocs
commit a8101a79af3a93646c545401b590911324aadbf0
Author: Alexander Bezzubov <[email protected]>
Date: 2016-06-27T11:05:05Z
Python: refactoring - arrange imports
commit 0de53209786e958a047e003fb8f3d0996f3d1211
Author: Alexander Bezzubov <[email protected]>
Date: 2016-06-27T11:43:09Z
Python: refactoring open port checking
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
