You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Di Xu (Jira)" <ji...@apache.org> on 2020/10/09 05:46:00 UTC
[jira] [Updated] (FLINK-19549) [CI] ##[error]The job running on
agent Azure Pipelines 5 ran longer than the maximum time of 260 minutes.
[ https://issues.apache.org/jira/browse/FLINK-19549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Di Xu updated FLINK-19549:
--------------------------
Description:
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]
was:
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
> [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)