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 2017/05/22 09:23:04 UTC
[jira] [Closed] (FLINK-6635) ClientConnectionTest is broken because
the ClusterClient lazily connects to the JobManager
[ https://issues.apache.org/jira/browse/FLINK-6635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-6635.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
1.3.0
1.4.0: e3979616b4cd40db8f96bd661d52c37fcf84d57c
1.3.0: 77c02fe394def7accd90409fd243210e86c630af
> ClientConnectionTest is broken because the ClusterClient lazily connects to the JobManager
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-6635
> URL: https://issues.apache.org/jira/browse/FLINK-6635
> Project: Flink
> Issue Type: Bug
> Components: Client, Tests
> Affects Versions: 1.3.0, 1.4.0
> Reporter: Till Rohrmann
> Assignee: Till Rohrmann
> Priority: Minor
> Fix For: 1.3.0, 1.4.0
>
>
> The {{ClientConnectionTest}} is broken since the refactoring of the {{ClusterClient}}. The reason is that we expect an exception to be thrown which contains the word "JobManager". However, in case that the created {{ClusterClient}} does not fail, we fail the test with a message containing "JobManager". That is the reason why this test passed even though it actually failed all the time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)