You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Dong Lin (Jira)" <ji...@apache.org> on 2023/04/19 01:52:00 UTC

[jira] [Commented] (FLINK-27535) Optimize the unit test execution time

    [ https://issues.apache.org/jira/browse/FLINK-27535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713837#comment-17713837 ] 

Dong Lin commented on FLINK-27535:
----------------------------------

Merged to apache/flink-ml master branch d08b75bacb5a04fa6259b8cc552408dcfea60a94

> Optimize the unit test execution time
> -------------------------------------
>
>                 Key: FLINK-27535
>                 URL: https://issues.apache.org/jira/browse/FLINK-27535
>             Project: Flink
>          Issue Type: Improvement
>          Components: Library / Machine Learning
>            Reporter: Dong Lin
>            Assignee: Yunfeng Zhou
>            Priority: Critical
>              Labels: pull-request-available
>
> Currently `mvn package` takes 10 minutes to complete in Github actions. A lot of time is spent in running unit tests for algorithms. For example, LogisticRegressionTest takes 82 seconds and KMeansTest takes 43 seconds in [1]. 
> This time appears to be more than expected. And it will considerably reduce developer velocity if a developer needs to wait for hours to get test results once we have 100+ algorithms in Flink ML.
> We should understand why it takes 82 seconds to run e.g. LogisticRegressionTest and see if there is a way to optimize the test execution time.
> [1] https://github.com/apache/flink-ml/runs/6319402103?check_suite_focus=true.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)