[
https://issues.apache.org/jira/browse/GEODE-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16749066#comment-16749066
]
ASF subversion and git services commented on GEODE-6183:
--------------------------------------------------------
Commit 654dc3bac3e50e66f33385bdbc38c88750061aa9 in geode's branch
refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=654dc3b ]
GEODE-6297: Add Process info to Launcher status failure msg
This will provide some details about if the process is actually
alive or not when FileProcessController.status throws
IllegalStateException.
When the test fails again, if Process is not alive then the
underlying cause is probably something like a BindException
preventing the startup of the Locator process.
This info will also apply to GEODE-6183 which is nearly
identical.
I'm including the change in ServerLauncherRemoteIntegrationTestCase
as well in case there's ever a similar failure starting up a
server.
> CI Failure:
> LocatorLauncherRemoteFileIntegrationTest.startDeletesStaleControlFiles failed
> with ConditionTimeoutException
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-6183
> URL: https://issues.apache.org/jira/browse/GEODE-6183
> Project: Geode
> Issue Type: Bug
> Components: ci, gfsh
> Reporter: Eric Shu
> Assignee: Kirk Lund
> Priority: Major
>
> Test failed in
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/IntegrationTestOpenJDK8/builds/223
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest >
> startDeletesStaleControlFiles FAILED
> org.awaitility.core.ConditionTimeoutException: Assertion condition
> defined as a lambda expression in
> org.apache.geode.distributed.LocatorLauncherRemoteIntegrationTestCase that
> uses org.apache.geode.distributed.LocatorLauncher expected:<[online]> but
> was:<[not responding]> within 300 seconds.
> Caused by:
> org.junit.ComparisonFailure: expected:<[online]> but was:<[not
> responding]>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
