[
https://issues.apache.org/jira/browse/FLINK-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205902#comment-17205902
]
Dian Fu commented on FLINK-18366:
---------------------------------
slow run:
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=7153&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee&t=ff888d9b-cd34-53cc-d90f-3e446d355529
> 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
>
> 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)
