You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matyas Orhidi (Jira)" <ji...@apache.org> on 2022/06/14 14:39:00 UTC

[jira] [Updated] (FLINK-28059) Parallelize e2e tests

     [ https://issues.apache.org/jira/browse/FLINK-28059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matyas Orhidi updated FLINK-28059:
----------------------------------
    Description: 
Motivation:
 * Tests are running in a loop within a single step
 * It takes 15mins for the e2e tests to finish
 * We could run up to 256 parallel tasks instead of the current 6
 * Without looking at the logs it is hard to spot/verify which exact tests are running during e2e CI workflows

Suggestions:
 * Let's add the tests into an extra dimension of the test matrix instead of looping
 * Try to find a way to share the common steps before/after the tests

  was:
Motivation:
 * Tests are running in a loop within a single step
 * It takes 15mins for the e2e tests to finish
 * We could run 256 parallel tasks instead of the current 6
 * Without looking at the logs it is hard to spot/verify which exact tests are running during e2e CI workflows

Suggestions:
 * Let's add the tests into an extra dimension of the test matrix instead of looping
 * Try to find a way to share the common steps before/after the tests


> Parallelize e2e tests
> ---------------------
>
>                 Key: FLINK-28059
>                 URL: https://issues.apache.org/jira/browse/FLINK-28059
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>    Affects Versions: kubernetes-operator-1.1.0
>            Reporter: Matyas Orhidi
>            Priority: Major
>
> Motivation:
>  * Tests are running in a loop within a single step
>  * It takes 15mins for the e2e tests to finish
>  * We could run up to 256 parallel tasks instead of the current 6
>  * Without looking at the logs it is hard to spot/verify which exact tests are running during e2e CI workflows
> Suggestions:
>  * Let's add the tests into an extra dimension of the test matrix instead of looping
>  * Try to find a way to share the common steps before/after the tests



--
This message was sent by Atlassian Jira
(v8.20.7#820007)