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

Flink Jira Bot updated FLINK-18366:
-----------------------------------
      Labels: auto-deprioritized-major auto-unassigned  (was: auto-unassigned 
stale-major)
    Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so 
it is being deprioritized. If this ticket is actually Major, please raise the 
priority and ask a committer to assign you the issue or revive the public 
discussion.


> Track E2E test durations centrally
> ----------------------------------
>
>                 Key: FLINK-18366
>                 URL: https://issues.apache.org/jira/browse/FLINK-18366
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System / CI
>            Reporter: Robert Metzger
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned
>
> Every now and then, our E2E tests start timing out (see FLINK-16795), because 
> they hit the currently configured time-limit.
> To better understand what the expected E2E time, and potential performance 
> regressions, we should track the test execution duration centrally.



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

Reply via email to