Details
-
Test
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
this is different from GEODE-6784 because the startup rule returns failure, rather than a timeout being exceeded:
org.apache.geode.management.internal.rest.StandaloneClientManagementAPIAcceptanceTest > clientCreatesRegionUsingClusterManagementService[1] FAILED org.junit.ComparisonFailure: [Exit value from process started by [startCluster: gfsh -e start locator --port=28921 --http-service-port=28922 --J=-Dgemfire.JMX_MANAGER_PORT=28923 -e start server --locators=localhost[28921] --server-port=0]] expected:<[0]> but was:<[1]> at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:103) at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:143) at org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:152) at org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:153) at org.apache.geode.management.internal.rest.StandaloneClientManagementAPIAcceptanceTest.clientCreatesRegionUsingClusterManagementService(StandaloneClientManagementAPIAcceptanceTest.java:115)