[
https://issues.apache.org/jira/browse/FLINK-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290939#comment-17290939
]
Dawid Wysakowicz commented on FLINK-21503:
------------------------------------------
I think it might be caused by https://issues.apache.org/jira/browse/FLINK-19463
It is the bigger batch of changes after last successful run. Moreover I
compared tests times of the failed case and the last successful one and I see
some long running tests introduced in FLINK-19463 such as e.g.
{{org.apache.flink.contrib.streaming.state.EmbeddedRocksDBStateBackendTest}}
[~sjwiesman] Could you take a look?
> Tests time out on azure
> -----------------------
>
> Key: FLINK-21503
> URL: https://issues.apache.org/jira/browse/FLINK-21503
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends, Tests
> Reporter: Dawid Wysakowicz
> Priority: Major
> Labels: test-stability
>
> Both test_ci legacy_slot_management and test_ci
> finegrained_resource_management time out on azure
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=13731&view=logs&j=a57e0635-3fad-5b08-57c7-a4142d7d6fa9
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
