flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-5331) PythonPlanBinderTest idling extremely long
Date Tue, 13 Dec 2016 15:51:58 GMT
Till Rohrmann created FLINK-5331:

             Summary: 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

When running {{mvn clean verify}} locally, the {{PythonPlanBinderTest}} takes sometimes extremely
long to finish. The latest build took more than 900 seconds to complete.

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

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

View raw message