[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427912#comment-17427912 ]
ASF subversion and git services commented on GEODE-9701: -------------------------------------------------------- Commit 02e4baaadcd1fe7c076a445aa977b3c604d8eabc in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=02e4baa ] GEODE-9701: Support lower VM counts in ClusterStartupRule > ClusterStartupRule starts 4 VMs even if fewer VMs is specified > -------------------------------------------------------------- > > Key: GEODE-9701 > URL: https://issues.apache.org/jira/browse/GEODE-9701 > Project: Geode > Issue Type: Bug > Components: tests > Reporter: Kirk Lund > Assignee: Kirk Lund > Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > Bill reported that ClusterStartupRule seems to be creating 4 VMs no matter > how few VMs he specifies in a new test for [PR > #6930|https://github.com/apache/geode/pull/6930]. The concern is that by > creating more VMs, we are causing unnecessary load on machines in the cloud. > I wrote this simple test which confirms the problem: > {noformat} > import static org.apache.geode.test.dunit.VM.getVMCount; > import static org.assertj.core.api.Assertions.assertThat; > import org.junit.Rule; > import org.junit.Test; > import org.apache.geode.test.dunit.rules.ClusterStartupRule; > public class ClusterStartupRuleVmCountDistributedTest { > @Rule > public ClusterStartupRule clusterStartupRule = new ClusterStartupRule(3); > @Test > public void limitsVMsTo3() { > assertThat(getVMCount()).isEqualTo(3); > } > } > {noformat} > But if I replace {{ClusterStartupRule}} with {{DistributedRule}}, it passes > so the problem is specific to {{ClusterStartupRule}}. -- This message was sent by Atlassian Jira (v8.3.4#803005)