You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "shijinkui (JIRA)" <ji...@apache.org> on 2017/01/26 07:43:24 UTC
[jira] [Created] (FLINK-5650) flink-python unit test costs more
than half hour
shijinkui created FLINK-5650:
--------------------------------
Summary: flink-python unit test costs more than half hour
Key: FLINK-5650
URL: https://issues.apache.org/jira/browse/FLINK-5650
Project: Flink
Issue Type: Bug
Components: Python API
Reporter: shijinkui
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.4#6332)