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

Jens Deppe commented on GEODE-5228:
-----------------------------------

Another failure noted:

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.173/test-results/integrationTest/1542729826/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Test report artifacts from this job are available at:

http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.173/test-artifacts/1542729826/integrationtestfiles-OpenJDK8-1.9.0-build.173.tgz

> Existing or stale status file can potentially be read instead of the correct 
> status response file
> -------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-5228
>                 URL: https://issues.apache.org/jira/browse/GEODE-5228
>             Project: Geode
>          Issue Type: Bug
>          Components: management
>    Affects Versions: 1.1.0
>            Reporter: Kirk Lund
>            Assignee: Jason Huynh
>            Priority: Minor
>              Labels: ServerLauncher, ci, flaky, pull-request-available, swat
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The following test runs into a product race condition where the stale status 
> file can possibly be read before the server launcher has a chance to start up.
> A work around for the issue is to ask for the status a second time.  The 
> first time may read the incorrect status file.
> {noformat}
> ServerLauncherRemoteFileIntegrationTest fails intermittently with 
> IllegalStateException vf.gf.server.status is blank
> java.lang.IllegalStateException: Status file 
> '/tmp/build/ae3c03f4/built-geode/tmp/junit5775773082469887234/vf.gf.server.status'
>  is blank
>       at 
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:152)
>       at 
> org.apache.geode.internal.process.FileProcessController.status(FileProcessController.java:89)
>       at 
> org.apache.geode.distributed.ServerLauncher.statusWithWorkingDirectory(ServerLauncher.java:1102)
>       at 
> org.apache.geode.distributed.ServerLauncher.status(ServerLauncher.java:1050)
>       at 
> org.apache.geode.distributed.ServerLauncherRemoteIntegrationTestCase.lambda$awaitStart$1(ServerLauncherRemoteIntegrationTestCase.java:198)
>       at 
> org.awaitility.core.AssertionCondition$1.eval(AssertionCondition.java:55)
>       at 
> org.awaitility.core.ConditionAwaiter$ConditionPoller.run(ConditionAwaiter.java:215)
>       at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>       at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>       at java.lang.Thread.run(Thread.java:748)
> {noformat}



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

Reply via email to