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

Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/09/29 08:07:00 UTC

[jira] [Commented] (FLINK-19014) Investigate minimum e2e test duration

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

Robert Metzger commented on FLINK-19014:
----------------------------------------

Reduced the time to launch a flink job a tiny bit in: https://github.com/apache/flink/commit/b4ac5c626877d6e78ba01a36b067764671621c29

> Investigate minimum e2e test duration
> -------------------------------------
>
>                 Key: FLINK-19014
>                 URL: https://issues.apache.org/jira/browse/FLINK-19014
>             Project: Flink
>          Issue Type: Task
>          Components: Tests
>            Reporter: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, the minimum time for an e2e test is roughly 30 seconds.
> This even applies to tests that start a tiny cluster and only run a WordCount.
> It would be good to understand what exactly causes these tests to run for such a long time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)