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

2018-04-18 Thread apachegeodeci 
Pipeline results can be found at:

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

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

2018-04-18 Thread Spring CI 

---
Spring Data GemFire > Nightly-ApacheGeode > #891 was successful.
---
Scheduled
2386 tests in total.

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





--
This message is automatically generated by Atlassian Bamboo

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

2018-04-18 Thread apachegeodeci 
Pipeline results can be found at:

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

re: 1.6.0 release

2018-04-18 Thread Bruce Schuchardt 
A couple of people have reported running into GEODE-5085 
, which prevents a 
server from rejoining the cluster if it gets kicked out and a 
SecurityManager has been configured.


Is this something we could get into the 1.6 release?  The fix is a 
single commit and it's been through precheckin testing a few times now.

re: 1.6.0 release

2018-04-18 Thread Michael Stolz 
Yes please. I'm holding the build til this gets in. Please notify me here
when it's ready

--
Mike Stolz
Principal Engineer - Gemfire Product Manager
Mobile: 631-835-4771

On Apr 18, 2018 8:05 PM, "Bruce Schuchardt"  wrote:

> A couple of people have reported running into GEODE-5085 <
> https://issues.apache.org/jira/browse/GEODE-5085>, which prevents a
> server from rejoining the cluster if it gets kicked out and a
> SecurityManager has been configured.
>
> Is this something we could get into the 1.6 release?  The fix is a single
> commit and it's been through precheckin testing a few times now.
>
>
>