[
https://issues.apache.org/jira/browse/FLINK-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shijinkui updated FLINK-5650:
-----------------------------
Summary: Flink-python tests executing cost too long time (was:
Flink-python tests can time out)
> Flink-python tests executing cost too long time
> -----------------------------------------------
>
> Key: FLINK-5650
> URL: https://issues.apache.org/jira/browse/FLINK-5650
> Project: Flink
> Issue Type: Bug
> Components: Python API, Tests
> Affects Versions: 1.2.0
> Reporter: shijinkui
> Priority: Critical
> Fix For: 1.2.1
>
>
> When execute `mvn clean test` in flink-python, it will wait more than half
> hour after the console output below:
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> 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.
> The stack below:
> "main" prio=5 tid=0x00007f8d7780b800 nid=0x1c03 waiting on condition
> [0x0000700009fd8000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at
> org.apache.flink.python.api.streaming.plan.PythonPlanStreamer.startPython(PythonPlanStreamer.java:70)
> at
> org.apache.flink.python.api.streaming.plan.PythonPlanStreamer.open(PythonPlanStreamer.java:50)
> at
> org.apache.flink.python.api.PythonPlanBinder.startPython(PythonPlanBinder.java:211)
> at
> org.apache.flink.python.api.PythonPlanBinder.runPlan(PythonPlanBinder.java:141)
> at
> org.apache.flink.python.api.PythonPlanBinder.main(PythonPlanBinder.java:114)
> at
> org.apache.flink.python.api.PythonPlanBinderTest.testProgram(PythonPlanBinderTest.java:83)
> at
> org.apache.flink.test.util.JavaProgramTestBase.testJobWithoutObjectReuse(JavaProgramTestBase.java:174)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
