You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/04/15 12:23:25 UTC

[jira] [Updated] (FLINK-3764) LeaderChangeStateCleanupTest.testStateCleanupAfterListenerNotification fails on Travis

     [ https://issues.apache.org/jira/browse/FLINK-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-3764:
---------------------------------
    Description: 
The {{LeaderChangeStateCleanupTest.testStateCleanupAfterListenerNotification}} fails spuriously on Travis because of a {{NullPointerException}}. The reason is that it's not properly waited until the {{ResourceManager}} has been started. Due to this, it can happen that a leader notification message is tried to be sent to a {{LeaderRetrievalListener}} which has not been set by the {{ResourceManager}}.

[1] https://s3.amazonaws.com/archive.travis-ci.org/jobs/123271732/log.txt

  was:The {{LeaderChangeStateCleanupTest.testStateCleanupAfterListenerNotification}} fails spuriously on Travis because of a {{NullPointerException}}. The reason is that it's not properly waited until the {{ResourceManager}} has been started. Due to this, it can happen that a leader notification message is tried to be sent to a {{LeaderRetrievalListener}} which has not been set by the {{ResourceManager}}.


> LeaderChangeStateCleanupTest.testStateCleanupAfterListenerNotification fails on Travis
> --------------------------------------------------------------------------------------
>
>                 Key: FLINK-3764
>                 URL: https://issues.apache.org/jira/browse/FLINK-3764
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Critical
>              Labels: test-stability
>
> The {{LeaderChangeStateCleanupTest.testStateCleanupAfterListenerNotification}} fails spuriously on Travis because of a {{NullPointerException}}. The reason is that it's not properly waited until the {{ResourceManager}} has been started. Due to this, it can happen that a leader notification message is tried to be sent to a {{LeaderRetrievalListener}} which has not been set by the {{ResourceManager}}.
> [1] https://s3.amazonaws.com/archive.travis-ci.org/jobs/123271732/log.txt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)