[
https://issues.apache.org/jira/browse/FLINK-19964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17229290#comment-17229290
]
Arvid Heise commented on FLINK-19964:
-------------------------------------
I can confirm [~roman_khachatryan]'s find that this is caused by
e17dbab24f4f71c5472d27267e938791686e45c3. It's easy to produce locally.
I'm assuming recent commits just changed the timing and made it more likely to
appear.
However, it's also interesting that locally, the test only gets stuck after >10
tests are run on the same mini cluster. So it may also be related to some
memory leaks.
> Gelly ITCase stuck on Azure in HITSITCase.testPrintWithRMatGraph
> ----------------------------------------------------------------
>
> Key: FLINK-19964
> URL: https://issues.apache.org/jira/browse/FLINK-19964
> Project: Flink
> Issue Type: Bug
> Components: Library / Graph Processing (Gelly), Runtime / Network,
> Tests
> Affects Versions: 1.12.0
> Reporter: Chesnay Schepler
> Assignee: Arvid Heise
> Priority: Blocker
> Labels: test-stability
> Fix For: 1.12.0
>
>
> The HITSITCase has gotten stuck on Azure. Chances are that something in the
> scheduling or network has broken it.
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=8919&view=logs&j=c5f0071e-1851-543e-9a45-9ac140befc32&t=1fb1a56f-e8b5-5a82-00a0-a2db7757b4f5
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
