Build for version 1.6.0-build.642 of Apache Geode failed.

2018-03-16 Thread apachegeodeci
= The build job for Apache Geode version 1.6.0-build.642 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.6.0-build.642/geode-build-artifacts-1.6.0-build.642.tgz

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

2018-03-16 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/289

Build failed in Jenkins: Geode-nightly #1135

2018-03-16 Thread Apache Jenkins Server
See Changes: [sai.boorlagaddai] GEODE-4830: use POJOs to represent cache configuration allowed by [sai.boorlagaddai] GEODE-4830: use CacheConfig to access the jndi list in [github] GEODE-4870: Categorize AlterAsy

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

2018-03-16 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/DistributedTest/builds/8

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

2018-03-16 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/206

Errored: apache/geode-native#887 (develop - 03b6be2)

2018-03-16 Thread Travis CI
Build Update for apache/geode-native - Build: #887 Status: Errored Duration: 49 minutes and 23 seconds Commit: 03b6be2 (develop) Author: Jacob Barrett Message: GEODE-4851: Reduce layers in Docker image. View the changeset: https://github.com/apache/geode-nati

Build for version 1.6.0-build.640 of Apache Geode failed.

2018-03-16 Thread apachegeodeci
= The build job for Apache Geode version 1.6.0-build.640 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.6.0-build.640/geode-build-artifacts-1.6.0-build.640.tgz

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

2018-03-16 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/IntegrationTest/builds/7

Build for version 1.6.0-build.637 of Apache Geode failed.

2018-03-16 Thread apachegeodeci
= The build job for Apache Geode version 1.6.0-build.637 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.6.0-build.637/geode-build-artifacts-1.6.0-build.637.tgz

Build for version 1.6.0-build.636 of Apache Geode failed.

2018-03-16 Thread apachegeodeci
= The build job for Apache Geode version 1.6.0-build.636 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.6.0-build.636/geode-build-artifacts-1.6.0-build.636.tgz

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

2018-03-16 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #858 was successful. --- Scheduled 2381 tests in total. https://build.spring.io/browse/SGF-NAG-858/ -- This

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

2018-03-16 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/321

Re: Please use Awaitilty instead of Thread.sleep

2018-03-16 Thread Jens Deppe
My bad. Thanks for pointing that out Kirk. On Fri, Mar 16, 2018 at 11:22 AM, Kirk Lund wrote: > I can't believe we're still checking in new tests with Thread.sleep of 10 > seconds instead of using Awaitility. > > org.apache.geode.management.internal.configuration. > ClusterConfigLocatorRestartDU

Please use Awaitilty instead of Thread.sleep

2018-03-16 Thread Kirk Lund
I can't believe we're still checking in new tests with Thread.sleep of 10 seconds instead of using Awaitility. org.apache.geode.management.internal.configuration.ClusterConfigLocatorRestartDUnitTest In both test methods: // Wait some time to reconnect Thread.sleep(1); Please don't d