[
https://issues.apache.org/jira/browse/FLINK-19549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song reopened FLINK-19549:
----------------------------------
Reopen this issue because the problem still exist.
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=7659&view=results
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=7686&view=results
The time limit has been increased recently in FLINK-16795, but there are still
many timeouts. Maybe we should consider split the e2e into multiple stages?
[~rmetzger], WDYT?
> [CI] ##[error]The job running on agent Azure Pipelines 5 ran longer than the
> maximum time of 260 minutes.
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-19549
> URL: https://issues.apache.org/jira/browse/FLINK-19549
> Project: Flink
> Issue Type: Task
> Components: Build System / CI
> Reporter: Di Xu
> Priority: Blocker
>
> The CI pipeline has a timeout of 260 minutes, which is not enough after we
> add more e2e tests such as run #20201008.12[1] for FLINK-17613.
> Actually 260 minutes is barely enough for current jobs, the latest successful
> run[2] already takes 249 minutes. So please consider for a longer timeout.
> [1][https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=7290&view=logs&j=c88eea3b-64a0-564d-0031-9fdcd7b8abee]
>
> [2][https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=7304&view=logs&j=52b61abe-a3cc-5bde-cc35-1bbe89bb7df5]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
