Need information about vf.gf.locator.status.cmd & vf.gf.locator.status.cmd

[Dinesh Akhand]

Hi Team,

What is vf.gf.locator.status.cmd , vf.gf.locator.status.cmd file ,which are 
getting created in locator working dir.
I am trying to understand it , in what scenario these file are getting created.

Both files are empty  and locator is going down.
Could you please provide information about these files.

Thanks,
Dinesh Akhand

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

Re: Need information about vf.gf.locator.status.cmd & vf.gf.locator.status.cmd

[Jens Deppe]

Hi Dinesh

vf.gf.locator.status.cmd and vf.gf.locator.stop.cmd are 'watchdog' files
used to send commands to the locator. In this case, they are used to
request status and to request the locator to stop. There are similar files,
called vf.gf.server.* for the servers. These are just internal files and
should not be changed or deleted by the user.

--Jens

On Tue, May 29, 2018 at 4:08 AM, Dinesh Akhand  wrote:

> Hi Team,
>
> What is vf.gf.locator.status.cmd , vf.gf.locator.status.cmd file ,which
> are getting created in locator working dir.
> I am trying to understand it , in what scenario these file are getting
> created.
>
> Both files are empty  and locator is going down.
> Could you please provide information about these files.
>
> Thanks,
> Dinesh Akhand
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
>
> you may review at https://www.amdocs.com/about/email-disclaimer <
> https://www.amdocs.com/about/email-disclaimer>
>

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #932 was SUCCESSFUL (with 2406 tests)

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #932 was successful.
---
Scheduled
2408 tests in total.

https://build.spring.io/browse/SGF-NAG-932/





--
This message is automatically generated by Atlassian Bamboo

Geode unit tests 'develop/UITests' took too long to execute

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/37

Geode unit tests 'develop/UITests' took too long to execute

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/38

Geode unit tests completed in 'develop/IntegrationTest' with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/29

Geode unit tests 'develop/AcceptanceTest' took too long to execute

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/37

Geode unit tests 'develop/DistributedTest' took too long to execute

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/26