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 2018/04/03 14:38:00 UTC

[jira] [Closed] (FLINK-6567) ExecutionGraphMetricsTest fails on Windows CI

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

Till Rohrmann closed FLINK-6567.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.6.0)
                   1.5.0

Fixed via
master: db366cd3d02a823f93185f29ca7ae93da9e2a04b
1.5.0: 515069e14f770ebfb86df27dc27b858ded51c6d5

> ExecutionGraphMetricsTest fails on Windows CI
> ---------------------------------------------
>
>                 Key: FLINK-6567
>                 URL: https://issues.apache.org/jira/browse/FLINK-6567
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.3.0, 1.4.0
>            Reporter: Chesnay Schepler
>            Assignee: Till Rohrmann
>            Priority: Blocker
>              Labels: test-stability
>             Fix For: 1.5.0
>
>
> The {{testExecutionGraphRestartTimeMetric}} fails every time i run it on AppVeyor. It also very rarely failed for me locally.
> The test fails at Line 235 if the RUNNING timestamp is equal to the RESTARTING timestamp, which may happen when combining a fast test with a low resolution clock.
> A simple fix would be to increase the timestamp between RUNNING and RESTARTING by adding a 50ms sleep timeout into the {{TestingRestartStrategy#canRestart()}} method, as this one is called before transitioning to the RESTARTING state.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)