You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/08/02 22:15:00 UTC
[jira] [Commented] (GEODE-7040) Fix checked assertion and
connection parameters to
'FunctionReturnsObjectWhichCantBeDeserializedOnServer' test
[ https://issues.apache.org/jira/browse/GEODE-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16899243#comment-16899243 ]
ASF subversion and git services commented on GEODE-7040:
--------------------------------------------------------
Commit 01bd9307d3eaad20be11265807a5e945e6de6b96 in geode-native's branch refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=01bd930 ]
GEODE-7040: Fix negative test case for values which can't be deserialized on server (#506)
- test wasn't connecting to locator properly, so it was getting the wrong exception
Co-authored-by: Mike Martell <mm...@pivotal.io>
> Fix checked assertion and connection parameters to 'FunctionReturnsObjectWhichCantBeDeserializedOnServer' test
> --------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-7040
> URL: https://issues.apache.org/jira/browse/GEODE-7040
> Project: Geode
> Issue Type: Bug
> Components: native client
> Reporter: Blake Bender
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We found, in the course of developing another function execution test, that this one was attempting to connect to the locator on the wrong port, and was thus checking for the wrong exception at the end. Fix is pretty trivial, but it should go in on its own, hence the separate Jira ticket.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)