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

Posted to issues@flink.apache.org by "Kostas Kloudas (JIRA)" <ji...@apache.org> on 2016/09/29 16:35:21 UTC

[jira] [Commented] (FLINK-4700) Harden the TimeProvider test

    [ https://issues.apache.org/jira/browse/FLINK-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533260#comment-15533260 ] 

Kostas Kloudas commented on FLINK-4700:
---------------------------------------

[~StephanEwen] 

I am thinking that the best solution to this is to remove the testDefaultTimeProvider() test altogether.

The only thing it actually tests is the java ScheduledExecutorService and there is no way to make it stable 
without adding test-specific methods (visible for testing) in the DefaultTimeServiceProvider. 

What do you think?

> Harden the TimeProvider test
> ----------------------------
>
>                 Key: FLINK-4700
>                 URL: https://issues.apache.org/jira/browse/FLINK-4700
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>
> Currently the TimeProvider test fails due to a race condition. This task aims at fixing it.



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