[
https://issues.apache.org/jira/browse/FLINK-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler resolved FLINK-5331.
-------------------------------------
Resolution: Duplicate
Fix Version/s: 1.2.1
1.3.0
Let's assume that this is the same issue as FLINK-5650. Please re-open if you
experience it again [~till.rohrmann].
> PythonPlanBinderTest idling extremely long
> ------------------------------------------
>
> Key: FLINK-5331
> URL: https://issues.apache.org/jira/browse/FLINK-5331
> Project: Flink
> Issue Type: Improvement
> Components: Python API, Tests
> Affects Versions: 1.2.0
> Reporter: Till Rohrmann
> Priority: Minor
> Fix For: 1.3.0, 1.2.1
>
> Attachments: Screen Shot 2016-12-13 at 16.36.38.png
>
>
> When running {{mvn clean verify}} locally, the {{PythonPlanBinderTest}} takes
> sometimes extremely long to finish. The latest build took more than 900
> seconds to complete.
> {code}
> Running org.apache.flink.python.api.PythonPlanBinderTest
> log4j:WARN No appenders could be found for logger
> (org.apache.flink.python.api.PythonPlanBinderTest).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more
> info.
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 923.586 sec -
> in org.apache.flink.python.api.PythonPlanBinderTest
> Results :
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> {code}
> Additionally I see a lot of python processes (~ 70-80) on my system doing
> effectively nothing. This behaviour seems really strange to me. I think it
> would be great to revisit this test case to see whether we can streamline it
> a little bit better.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
