Brian Rowe created GEODE-5817:
---------------------------------
Summary: Acceptance test fails with org.junit.ComparisonFailure:
expected:<[0]> but was:<[1]>
Key: GEODE-5817
URL: https://issues.apache.org/jira/browse/GEODE-5817
Project: Geode
Issue Type: Bug
Reporter: Brian Rowe
This appears to be the same issue as GEODE-5601, however, this is still
occurring even when the acceptanceTests are being run serially (or at least,
run with the fix for 5601).
Example failures:
from
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/47
{noformat}org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest
> canStopServerByNameWhenConnectedOverHttp FAILED
org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:124)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:112)
at
org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest.startCluster(StopServerAcceptanceTest.java:32){noformat}
from
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/53
{noformat}org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest
> classMethod FAILED
org.junit.ComparisonFailure: expected:<[0]> but was:<[1]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at
org.apache.geode.test.junit.rules.gfsh.GfshExecution.awaitTermination(GfshExecution.java:124)
at
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:125)
at
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:133)
at
org.apache.geode.management.internal.cli.shell.StatusServerExitCodeAcceptanceTest.classSetup(StatusServerExitCodeAcceptanceTest.java:66){noformat}
Looking at the logs for these failures, we see the following in standard error:
{noformat}
The Cache Server process terminated unexpectedly with exit status 1. Please
refer to the log file in
/tmp/junit5496177071859309076/member-controller/server-lock-better-iota for
full details.
Exception in thread "main" java.lang.RuntimeException: An IO error occurred
while starting a Server in
/tmp/junit5496177071859309076/member-controller/server-lock-better-iota on
develop-acceptancetest-53.c.apachegeode-ci.internal[40404]: Network is
unreachable; port (40404) is not available on localhost.
at
org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:816)
at
org.apache.geode.distributed.ServerLauncher.run(ServerLauncher.java:704)
at
org.apache.geode.distributed.ServerLauncher.main(ServerLauncher.java:224)
Caused by: java.net.BindException: Network is unreachable; port (40404) is not
available on localhost.
at
org.apache.geode.distributed.AbstractLauncher.assertPortAvailable(AbstractLauncher.java:129)
at
org.apache.geode.distributed.ServerLauncher.start(ServerLauncher.java:761)
... 2 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
