You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/06/25 11:56:00 UTC
[jira] [Closed] (FLINK-12915) AbstractOperatorRestoreTestBase can
deadlock if one test fails
[ https://issues.apache.org/jira/browse/FLINK-12915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-12915.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
master: 08d8cf5b8dff8193c69c5dd3657112ce862054ea
> AbstractOperatorRestoreTestBase can deadlock if one test fails
> --------------------------------------------------------------
>
> Key: FLINK-12915
> URL: https://issues.apache.org/jira/browse/FLINK-12915
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends, Tests
> Affects Versions: 1.9.0
> Reporter: Till Rohrmann
> Assignee: Yun Tang
> Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The {{AbstractOperatorRestoreTestBase}} can deadlock in case of a failing test case. The problem is that if one test fails then the corresponding test job won't be canceled. Due to that a succeeding test case might not get enough slots to execute because the job of the failing test is still running. This leads to a deadlocked test as happened here: https://api.travis-ci.org/v3/job/548181384/log.txt
> A side effect is that the original test failure won't be properly displayed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)