[ https://issues.apache.org/jira/browse/GEODE-9220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343780#comment-17343780 ]
Geode Integration commented on GEODE-9220: ------------------------------------------ Seen in [WindowsIntegrationTestOpenJDK11 #209|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/209] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0234/test-results/integrationTest/1620881348/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0234/test-artifacts/1620881348/windows-integrationtestfiles-OpenJDK11-1.15.0-build.0234.tgz]. > Switch unit and integration tests to use JedisCluster > ----------------------------------------------------- > > Key: GEODE-9220 > URL: https://issues.apache.org/jira/browse/GEODE-9220 > Project: Geode > Issue Type: Test > Components: redis > Reporter: Jens Deppe > Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > This won't make sense for some commands that are not 'cluster aware' - for > example {{INFO}}. Commands that act on a key are all cluster aware. -- This message was sent by Atlassian Jira (v8.3.4#803005)