[
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-unassigned stale-major (was: auto-unassigned)
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-unassigned, stale-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)
