You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Ryan McMahon (Jira)" <ji...@apache.org> on 2019/09/04 17:44:00 UTC
[jira] [Resolved] (GEODE-7158) Singleton CacheClientNotifier state
can pollute tests causing failures
[ https://issues.apache.org/jira/browse/GEODE-7158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McMahon resolved GEODE-7158.
---------------------------------
Fix Version/s: 1.11.0
Assignee: Ryan McMahon
Resolution: Fixed
> Singleton CacheClientNotifier state can pollute tests causing failures
> ----------------------------------------------------------------------
>
> Key: GEODE-7158
> URL: https://issues.apache.org/jira/browse/GEODE-7158
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: Ryan McMahon
> Assignee: Ryan McMahon
> Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Two tests in the CacheClientNotifierTest class failed in this PR run:
> [https://concourse.apachegeode-ci.info/builds/92365]
> They both appear to be failing due to unexpected proxies in their proxy collections. Our best guess at this point is that these unexpected proxies are coming from a singleton CacheClientNotifier from a previous test. It is difficult to pinpoint which test might be causing this pollution, so our best course of action at this point is to shutdown any existing CacheClientNotifier singletons in the @Before method, so each test starts with a clean state.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)