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 2019/06/20 16:34:00 UTC
[jira] [Updated] (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 ]
Till Rohrmann updated FLINK-12915:
----------------------------------
Component/s: (was: API / Type Serialization System)
Runtime / State Backends
> 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
> Priority: Critical
> Labels: test-stability
>
> 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)