You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2017/02/28 18:41:45 UTC

[jira] [Resolved] (FLINK-5923) Test instability in SavepointITCase testTriggerSavepointAndResume

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

Stephan Ewen resolved FLINK-5923.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

Fixed via c24c7ec3332d0eb6ebb24eb70c9aabd055cc129f

Note: Wrong JIRA tag in commit message!

> Test instability in SavepointITCase testTriggerSavepointAndResume
> -----------------------------------------------------------------
>
>                 Key: FLINK-5923
>                 URL: https://issues.apache.org/jira/browse/FLINK-5923
>             Project: Flink
>          Issue Type: Test
>          Components: Tests
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>              Labels: test-stability
>             Fix For: 1.3.0
>
>
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/205042538/log.txt
> {code}
> Failed tests: 
>   SavepointITCase.testTriggerSavepointAndResume:258 Checkpoints directory not cleaned up: [/tmp/junit1029044621247843839/junit7338507921051602138/checkpoints/47fa12635d098bdafd52def453e6d66c/chk-4] expected:<0> but was:<1>
> {code}
> I think this is due to a race in the test. When shutting down the cluster it can happen that in progress checkpoints linger around.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)