[ 
https://issues.apache.org/jira/browse/GEODE-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16746875#comment-16746875
 ] 

Kirk Lund commented on GEODE-6297:
----------------------------------

Looks like both GEODE-6183 and GEODE-6297 have the same underlying failure in 
which FileProcessController.status throws IllegalStateException("Status file '" 
+ statusFile + "' is blank").

In both cases, the test is trying to start a Locator and then waits for its 
status using FileProcessController.

I suspect that the Locator failed to start, possibly due to a BindException, 
but the test infrastructure isn't sturdy enough to capture what the cause of 
failure was. I'm going to improve the failure message to indicate if the 
Process is running or not. If it's not running then that helps indicate that 
the Locator failed to start. At that point, I would need to improve the test 
infrastructure to try and capture logs or stderr in some way to verify 
BindException as the cause.

> CI failure: 
> LocatorLauncherRemoteFileIntegrationTest.statusWithPidReturnsOnlineWithDetails
> ------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6297
>                 URL: https://issues.apache.org/jira/browse/GEODE-6297
>             Project: Geode
>          Issue Type: Bug
>          Components: management
>            Reporter: Bruce Schuchardt
>            Assignee: Kirk Lund
>            Priority: Major
>              Labels: CI
>
> Failed in Windows CI run 
> [232|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK8/builds/232]
> {noformat}
> > Task :geode-core:integrationTest
> org.apache.geode.distributed.LocatorLauncherRemoteFileIntegrationTest > 
> statusWithPidReturnsOnlineWithDetails FAILED
>     java.lang.IllegalStateException: Status file 
> 'C:\Users\geode\AppData\Local\Temp\junit7623641902150852427\vf.gf.locator.status'
>  is blank
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to