[
https://issues.apache.org/jira/browse/FLINK-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322996#comment-17322996
]
Flink Jira Bot commented on FLINK-18366:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Robert Metzger
> Priority: Major
> Labels: stale-assigned
>
> 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)
