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

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/FlakyTest/builds/9

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

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/447

Re: 1.6.0 release

The GEODE-3926 commit has now been reverted on release 1.6.0 Lucene precheckin ran with no errors hence pushed to origin/release/1.6.0 branch. Will update one we get complete test run on the branch. Regards Nabarun On Thu, Apr 19, 2018 at 12:19 PM Nabarun Nag wrote: > Hi Mike > Sorry for the l

Re: [Discuss] Scope of the CacheElement interface with the respect to the public cluster configuration API

Hi there Patrick. I have not checked the wiki page, but if you have not updated that page with the proposal then could you possibly do that. I need to visualize the problem and reading a bunch of words does not visualize it for me. Visualizing it might actually help describe the future and e

[Proposal] Changes to the experimental cluster configuration API.

Hello, all! I would like to make a few changes to our experimental ClusterConfigurationService interface, focusing on better ease-of-use and matching intuition. The majority of these can be achieved very simply by regenerating our configuration objects from the cache XSD and passing a JAXB bind

[Discuss] Scope of the CacheElement interface with the respect to the public cluster configuration API

Hello all! We introduced the CacheElement interface as part of our experimental API to update the cluster configuration. I'd like to solidify and document our intent for the interface and the extent to which it is expected to apply. In its current form, the CacheElement interface extends Serl

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

--- Spring Data GemFire > Nightly-ApacheGeode > #892 was successful. --- Scheduled 2386 tests in total. https://build.spring.io/browse/SGF-NAG-892/ -- This

Re: [Proposal]: behavior change when region doesn't exist in cluster configuration

Ok. Yes we do have to take the leap :) Let's keep thinking that way. -- Mike Stolz Principal Engineer, GemFire Product Lead Mobile: +1-631-835-4771 Download the GemFire book here. On Thu, Apr 19, 2018 at 6:29 PM, Jinme

Re: [Proposal]: behavior change when region doesn't exist in cluster configuration

but this proposed change is one of the effort toward "deprecating cache.xml". I think we've got to take the leap at one point. On Thu, Apr 19, 2018 at 3:14 PM, Michael Stolz wrote: > Hmmm...I think I liked the old behavior better. It was a kind of bridge to > cluster config. > > I still thin

Re: [Proposal]: behavior change when region doesn't exist in cluster configuration

Hmmm...I think I liked the old behavior better. It was a kind of bridge to cluster config. I still think we need to be putting much more effort into deprecating cache.xml and much less effort into fixing the (possibly) hundreds of bugs related to using both cache.xml and cluster configuration at t

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

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/8

[Proposal]: behavior change when region doesn't exist in cluster configuration

Scenario: a locator with cluster configuration enabled and a server started with a cache.xml that has /regionA defined and connected to this locator. So the initial state is the locator has an empty cluster configuration for the cluster, but the server has a region defined in it's cache. Old behav

Re: 1.6.0 release

Hi Mike Sorry for the last email. "Send" got clicked . So for GEODE-3926 only two commits made into release/1.6.0 -75ae58423bc66ca127fec7d2fc3ad71fbed61094 -99caa3038b544ee444d6f151b4c0b9aa77204741 However these commits didn't make into release 1.6.0 - b71b79fe813b408fc50a172644007e2d5f54a1e2

Re: 1.6.0 release

Hi Mike, GEODE-3926 only two commits made into the release On Thu, Apr 19, 2018 at 10:49 AM Xiaojian Zhou wrote: > I have cherry-picked GEODE-5056 into 9.5 and 1.6.0 > > On Thu, Apr 19, 2018 at 9:09 AM, Bruce Schuchardt > wrote: > > > Thanks Mike - I've cherry-picked the fix onto the release/1

Re: 1.6.0 release

I have cherry-picked GEODE-5056 into 9.5 and 1.6.0 On Thu, Apr 19, 2018 at 9:09 AM, Bruce Schuchardt wrote: > Thanks Mike - I've cherry-picked the fix onto the release/1.6.0 branch > > > > On 4/18/18 5:11 PM, Michael Stolz wrote: > >> Yes please. I'm holding the build til this gets in. Please no

Re: 1.6.0 release

Thanks Mike - I've cherry-picked the fix onto the release/1.6.0 branch On 4/18/18 5:11 PM, Michael Stolz wrote: 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,