Build failed in Jenkins: Geode-nightly-flaky #153

See Changes: [upthewaterspout] GEODE-3568: User can set a LuceneSerializer through the Java API [upthewaterspout] GEODE-3240: Refactor LuceneSerializer to have only a toDocuments method [upthewaterspout] GE

Build failed in Jenkins: Geode-nightly #988

See Changes: [upthewaterspout] GEODE-3568: User can set a LuceneSerializer through the Java API [upthewaterspout] GEODE-3240: Refactor LuceneSerializer to have only a toDocuments method [upthewaterspout] GEODE-32

Errored: apache/geode-examples#96 (develop - bf9ab05)

Build Update for apache/geode-examples - Build: #96 Status: Errored Duration: 1 minute and 17 seconds Commit: bf9ab05 (develop) Author: Swapnil Bawaskar Message: bump version View the changeset: https://github.com/apache/geode-examples/compare/e55efcc77380...

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

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

Re: [VOTE] C++ standardize on return values only

Stick with the out variable on this one and any others like this that are consistent with the Java API. The primary goal was to remove the very odd void readInt(int& int) calls. > On Oct 18, 2017, at 3:08 PM, Mark Hanson wrote: > > Sorry about that last email... to begin again > > Hello

Re: [VOTE] C++ standardize on return values only

I have seen the uint8_t *, uint32_t tuple mostly with C-style system level calls (e.g., reading from a resource). Perhaps these could be allowed to remain as part of lowering impedance with a legacy API. Sarge > On 18 Oct, 2017, at 15:08, Mark Hanson wrote: > > Sorry about that last email...

Re: [VOTE] C++ standardize on return values only

Sorry about that last email... to begin again Hello All, So in doing some work on this subject, we have come across a case that David and I believed was worth raising for discussion. As one might expect, at some point, someone is going to pass in a buffer and a length into a function and

Re: [VOTE] C++ standardize on return values only

> On Oct 18, 2017, at 2:49 PM, Mark Hanson wrote: > So in doing some work on this subject, we have come across a case that > David and I believed was worth raising for discussion. > > As one might expect, at some point, someone is going to pass in a buffer > and a length into a function and exp

Re: [VOTE] C++ standardize on return values only

Hello All, So in doing some work on this subject, we have come across a case that David and I believed was worth raising for discussion. As one might expect, at some point, someone is going to pass in a buffer and a length into a function and expect data put into that buffer, e.g. On Tue, Oct 3

Errored: apache/geode-examples#96 (develop - bf9ab05)

Build Update for apache/geode-examples - Build: #96 Status: Errored Duration: 1 minute and 17 seconds Commit: bf9ab05 (develop) Author: Swapnil Bawaskar Message: bump version View the changeset: https://github.com/apache/geode-examples/compare/e55efcc77380...

Errored: apache/geode-examples#95 (rel/v1.3.0.RC3 - 4ff8f8e)

Build Update for apache/geode-examples - Build: #95 Status: Errored Duration: 1 minute and 29 seconds Commit: 4ff8f8e (rel/v1.3.0.RC3) Author: Swapnil Bawaskar Message: - removing SNAPSHOT from release version - change geode distribution extenstion from tar.gz

[VOTE] Apache Geode release - 1.3.0 RC3

This is the third release candidate for Apache Geode, version 1.3.0. Thanks to all the community members for their contributions to this release! *** Please download, test and vote by Monday, October 23, 0800 hrs US Pacific. *** It fixes 376 issues. release notes can be found at: https://issues.a

Re: DSFIDNotFoundException: Unknown DataSerializableFixedID: -158

I see what's wrong.  The new message needs to be registered in DSFIDFactory.  I'll get a fix checked in today. On 10/18/17 11:48 AM, Bruce Schuchardt wrote: I'm looking into this more.  I recently introduced DSFID -158 for the FinalCheckPassedMessage.  I added this DSFID to DataSerializableFi

Re: DSFIDNotFoundException: Unknown DataSerializableFixedID: -158

I'm looking into this more.  I recently introduced DSFID -158 for the FinalCheckPassedMessage.  I added this DSFID to DataSerializableFixedID and I can see that change in my commit but it's not in the source on develop. On 10/18/17 10:03 AM, Kirk Lund wrote: My latest sighting of this was

Re: [VOTE] Apache Geode release - 1.3.0 RC2

Ok, I will cut another release candidate. This vote is cancelled. However, we don't really ship the examples in the geode distribution (the examples is a different set of files: binary and src distributions). So, voting for 1.3 of geode, followed by voting for 1.3 of examples, I think should have w

Re: DSFIDNotFoundException: Unknown DataSerializableFixedID: -158

GEODE-3841 was opened to address this issue. Also complete logs of tests that ran before and after the failed test were also added in the comment section of the JIRA On Wed, Oct 18, 2017 at 10:10 AM Kirk Lund wrote: > Here's a log snippet with the failure -- looks like there's a UDP socket > WAR

Re: DSFIDNotFoundException: Unknown DataSerializableFixedID: -158

Here's a log snippet with the failure -- looks like there's a UDP socket WARN stack logged by this test before the ERROR stack. Is suspect string search no longer including WARN log statements? [vm2] [info 2017/10/17 21:03:46.296 UTC tid=0x1b] No locator(s) found with cluster configuration servic

Re: DSFIDNotFoundException: Unknown DataSerializableFixedID: -158

My latest sighting of this was in ResourceManagerDUnitTest.testRemoveDuringGetEntry which just shows this for previously run tests: Previously run tests: [ResourceManagerDUnitTest] On Tue, Oct 17, 2017 at 7:30 PM, Bruce Schuchardt wrote: > I think this is a secure UDP test leaving something beh

Re: geode and open JDK / newer version of java

Hi Roi, We've spent a little time doing some cursory testing with Java 9 and there are definitely some issues: - Compilation requires additional JVM args because of the new modularization in Java 9. - A few lambda syntaxes in tests need to be adjusted. - Some tests fail due to powermock issues. -

geode and open JDK / newer version of java

Hi, Has anyone tried to operate GEODE with open JDK - any version - rather than Oracle's JDK? Has anyone tried to operate GEODE with open JDK - specifically version 9 (released Sep 21 2017)? What about Oracle's version 9? Any migration issues, problems etc. ? Thanks, Roi This message and th