[
https://issues.apache.org/jira/browse/FLINK-20679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252896#comment-17252896
]
Till Rohrmann commented on FLINK-20679:
---------------------------------------
I think this test instability is caused by FLINK-10404. The problem is that the
{{SlotPool}} no longer eagerly accepts newly offered slots. With the
declarative resource management, it can happen that we are offering the slots
just in the moment when the job fails over. Since we are decreasing the
required resources when we are failing over, the offered slots can be rejected.
cc [~chesnay].
> JobMasterTest.testSlotRequestTimeoutWhenNoSlotOffering test failed
> ------------------------------------------------------------------
>
> Key: FLINK-20679
> URL: https://issues.apache.org/jira/browse/FLINK-20679
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.13.0
> Reporter: Huang Xingbo
> Priority: Critical
> Labels: test-stability
> Fix For: 1.13.0
>
>
> [https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=11055&view=logs&j=d89de3df-4600-5585-dadc-9bbc9a5e661c&t=19336553-69ec-5b03-471a-791a483cced6]
> {code:java}
> [ERROR] Failures:
> [ERROR] JobMasterTest.testSlotRequestTimeoutWhenNoSlotOffering:972
> Expected: a collection with size <1>
> but: collection size was <0>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)