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/158

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

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

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/248

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

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

Build for version 1.5.0-build.516 of Apache Geode failed.

= The build job for Apache Geode version 1.5.0-build.516 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.5.0-build.516/geode-build-artifacts-1.5.0-build.516.tgz

Re: Broken build?

Nevermind... On Thu, Feb 22, 2018 at 4:07 PM, Kirk Lund wrote: > My latest precheckin failed to compile with the following. This is on a > branch that I rebased on latest develop HEAD. Has this already been fixed? > > :gemfire-test:compileTestJava/tmp/build/ae3c03f4/gemfire/ > closed/gemfire-tes

Re: Broken build?

I got a similar issue a while back. It was something weird about gradle caching, I think. If you're using `./gradlew clean installDist`, try using a pass of `./gradlew clean build` instead. That cleared it up for me. On Thu, Feb 22, 2018 at 4:07 PM, Kirk Lund wrote: > My latest precheckin fai

Broken build?

My latest precheckin failed to compile with the following. This is on a branch that I rebased on latest develop HEAD. Has this already been fixed? :gemfire-test:compileTestJava/tmp/build/ae3c03f4/gemfire/closed/gemfire-test/src/test/java/parReg/execute/FunctionServiceTest.java:500: error: cannot f

Build for version 1.5.0-build.515 of Apache Geode failed.

= The build job for Apache Geode version 1.5.0-build.515 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.5.0-build.515/geode-build-artifacts-1.5.0-build.515.tgz

Re: Naming unit tests and integration tests

I've updated the page https://cwiki.apache.org/confluence/display/GEODE/Writing+tests -- please review and provide any feedback you may have. Sorry to take so long -- I went on PTO immediately after my previous message and finally got back to this task now. I'm planning to add in some test exampl

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

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

[SECURITY] CVE-2017-15696 Apache Geode configuration request authorization vulnerability

CVE-2017-15696 Apache Geode configuration request authorization vulnerability Severity: Important Vendor: The Apache Software Foundation Versions Affected: Apache Geode 1.0.0 through 1.3.0 Description: The Geode configuration service does not properly authorize configuration requests. This a

Errored: apache/geode#6325 (newFunctionService - 11e472d)

Build Update for apache/geode - Build: #6325 Status: Errored Duration: 4 minutes and 46 seconds Commit: 11e472d (newFunctionService) Author: Udo Kohlmeyer Message: Initial FS commit View the changeset: https://github.com/apache/geode/commit/11e472d1f55a View

Re: Logging in to concourse.apachegeode-ci.info

Yeah, the geode pipelines are completely public. You don't need to log into concourse to see anything, only to pause, kill or start jobs. Any changes made to the pipeline is done through the git repo, and those changes will be automatically pushed to concourse when merged. -S. On Wed, Feb 21, 201