[ https://issues.apache.org/jira/browse/FLINK-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452840#comment-16452840 ]
ASF GitHub Bot commented on FLINK-9243: --------------------------------------- GitHub user NicoK opened a pull request: https://github.com/apache/flink/pull/5915 [FLINK-9243][tests] fix flaky SuccessAfterNetworkBuffersFailureITCase this adds some `rebalance()` operations into `SuccessAfterNetworkBuffersFailureITCase#runKMeans` which should be set up to fail and at the same time allow `#runConnectedComponents()` to succeed. It appears, these two have been too close together regarding network buffer use before. I ran the test 500 times locally and it always succeeded now. You can merge this pull request into a Git repository by running: $ git pull https://github.com/NicoK/flink flink-9243 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/5915.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5915 ---- commit f78151b345bb297963c861135b1312ccfb1945cc Author: Nico Kruber <nico@...> Date: 2018-04-25T18:27:43Z [FLINK-9243][tests] fix flaky SuccessAfterNetworkBuffersFailureITCase ---- > SuccessAfterNetworkBuffersFailureITCase#testSuccessfulProgramAfterFailure is > unstable > ------------------------------------------------------------------------------------- > > Key: FLINK-9243 > URL: https://issues.apache.org/jira/browse/FLINK-9243 > Project: Flink > Issue Type: Bug > Components: Network, Tests > Affects Versions: 1.5.0 > Reporter: Sihua Zhou > Assignee: Nico Kruber > Priority: Blocker > Labels: test-stability > Fix For: 1.5.0 > > > There are some instances: > https://travis-ci.org/apache/flink/jobs/370121126 > https://travis-ci.org/apache/flink/jobs/370022111 > https://travis-ci.org/apache/flink/jobs/370055803 -- This message was sent by Atlassian JIRA (v7.6.3#76005)