[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified
[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Baker updated GEODE-9701: - Labels: GeodeOperationAPI pull-request-available testing (was: GeodeOperationAPI pull-request-available) > 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, testing > Fix For: 1.15.0 > > > 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.20.1#820001)
[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified
[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9701: -- Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI) > 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)
[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified
[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Labels: GeodeOperationAPI (was: GeodeOperationAPI needsTriage) > 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 > > 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)
[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified
[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Description: 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}}. was: 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]. 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}}. > 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 >Priority: Major > Labels: GeodeOperationAPI, needsTriage > > 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)
[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified
[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Labels: GeodeOperationAPI needsTriage (was: needsTriage) > 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 >Priority: Major > Labels: GeodeOperationAPI, needsTriage > > 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]. > 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)
[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified
[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Description: 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]. 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}}. was: Bill reported that ClusterStartupRule seems to be creating 4 VMs no matter how few VMs he specifies in a new test in PR #6930. This fails: {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}}. > 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 >Priority: Major > Labels: needsTriage > > 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]. > 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)
[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified
[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-9701: - Description: Bill reported that ClusterStartupRule seems to be creating 4 VMs no matter how few VMs he specifies in a new test in PR #6930. This fails: {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}}. was: This fails: {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}}. > 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 >Priority: Major > Labels: needsTriage > > Bill reported that ClusterStartupRule seems to be creating 4 VMs no matter > how few VMs he specifies in a new test in PR #6930. > This fails: > {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)
[jira] [Updated] (GEODE-9701) ClusterStartupRule starts 4 VMs even if fewer VMs is specified
[ https://issues.apache.org/jira/browse/GEODE-9701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-9701: - Labels: needsTriage (was: ) > 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 >Priority: Major > Labels: needsTriage > > This fails: > {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)