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

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

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #955 was SUCCESSFUL (with 2423 tests). Change made by John Blum.

--- Spring Data GemFire > Nightly-ApacheGeode > #955 was successful. --- Scheduled with changes by John Blum. 2425 tests in total. https://build.spring.io/browse

Re: OPLOG_MAGIC_SEQ_ID

Yea, I wouldn’t change this. Ideally each type of binary file would have a different magic seq to be easily distinguishable. Anthony > On Jun 21, 2018, at 3:01 PM, Kirk Lund wrote: > > Lesson: javadocs lie > > Do the two different values really need to be different? And because of > backwar

Re: OPLOG_MAGIC_SEQ_ID

Lesson: javadocs lie Do the two different values really need to be different? And because of backwards compatibility we're stuck with this. On Thu, Jun 21, 2018 at 1:49 PM, Anthony Baker wrote: > From a brief review of the source code, I believe that: > > DiskInitFile.OPLOG_MAGIC_SEQ_ID

Resolving geode-pulse compilation errors in IntelliJ

After the recent Gradle upgrade, you might see some compilation errors in IntelliJ involving geode-pulse such as the following: /Users/klund/dev/gemfire/open/geode-pulse/src/main/java/org/ apache/geode/tools/pulse/internal/service/MemberDetailsService.java Error:(28, 46) java: package org.springfr

Re: Revert recent Gradle upgrade

The long build time might be due to the old version of gradle daemon (pre 4.8). Try kill it if you have one running. On Thu, Jun 21, 2018 at 1:42 PM Jacob Barrett wrote: > I am suffering quite the opposite with 8.4 and seeing much longer build > times and rebuilds on things that have not changed

Re: OPLOG_MAGIC_SEQ_ID

From a brief review of the source code, I believe that: DiskInitFile.OPLOG_MAGIC_SEQ_ID is used for *.if files Oplog.OPLOG_MAGIC_SEQ_ID is used for all other oplog file types HTH, Anthony > On Jun 21, 2018, at 1:36 PM, Kirk Lund wrote: > > Please help me understand OPLOG_MAG

Re: Revert recent Gradle upgrade

I am suffering quite the opposite with 8.4 and seeing much longer build times and rebuilds on things that have not changed. > On Jun 21, 2018, at 12:47 PM, Jens Deppe wrote: > > I have a fix which I think will resolve the current problems: > https://github.com/apache/geode/pull/2074 (currently

OPLOG_MAGIC_SEQ_ID

Please help me understand OPLOG_MAGIC_SEQ_ID in the oplog code... There is a constant called OPLOG_MAGIC_SEQ_ID which is a byte representing the beginning of every oplog file. Makes sense so far. There are two different constants called OPLOG_MAGIC_SEQ_ID each with a different value. One is in Op

DataEngConf 2018

Hi Apache Geode Community, Wanted to send out a link to a talk I gave at DataEncConf 2018 entitled "What the heck is an In-Memory Data Grid?" The talk highlights Apache Geode and the IMDG space. https://www.youtube.com/watch?v=gAw5MVdIhbQ If you haven't heard of DataEngConf (http://www.dataengc

Re: Revert recent Gradle upgrade

I have a fix which I think will resolve the current problems: https://github.com/apache/geode/pull/2074 (currently running precheckin). It does require deferring IntelliJ's build to gradle (which may slow some tasks down a bit) but will at least let you continue to work. The perceived slowdown sh

Revert recent Gradle upgrade

I think we should revert the recent Gradle upgrade. This change apparently causes IntelliJ to not be able to build Geode which prevents us from running any Tests in the IDE. I'd prefer to fix how IntelliJ works with our project but we cannot be without the ability to debug tests. I don't know enou

package org.springframework.stereotype does not exist

Last week, I was able to build and execute tests in IntelliJ, but after pulling latest changes on develop (include the Gradle upgrade) I'm now getting errors in every class that uses org.springframework classes. Any ideas how to fix this? /Users/klund/dev/gemfire/open/geode-pulse/src/main/java/or

Build failed in Jenkins: Geode-nightly #1231

See Changes: [nag] GEODE-5109: Ignoring the test [github] GEODE-5333: Destroy failed connection in ConnectionConnector (#2072) -- [...truncated 41.95 KB...] Note: Some input