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

Flink Jira Bot updated FLINK-19014:
-----------------------------------
    Labels: auto-deprioritized-major pull-request-available stale-minor  (was: 
auto-deprioritized-major pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Investigate minimum e2e test duration
> -------------------------------------
>
>                 Key: FLINK-19014
>                 URL: https://issues.apache.org/jira/browse/FLINK-19014
>             Project: Flink
>          Issue Type: Improvement
>          Components: Tests
>            Reporter: Chesnay Schepler
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available, 
> stale-minor
>
> 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.20.1#820001)

Reply via email to