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

Build failed in Jenkins: Geode-nightly #1147

See Changes: [github] Feature/geode 4782 (#1682) [bschuchardt] Revert "GEODE-4822 The second server instance startup error: Could not [bschuchardt] Revert "GEODE-4822 The second server instance startup error: Co

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

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

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

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

Can I please get access to start jobs in concourse? my github username is sbawaska On Thu, Feb 22, 2018 at 10:24 AM Sean Goller wrote: > 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

Re: Geode unit tests 'develop/DistributedTest' took too long to execute

These timeouts are due to a hang in a query test that seem to be caused by the pdx-read-serialized work I checked in earlier this week.  I'm reverting those changes until I can figure out why this is happening. On 3/27/18 2:12 PM, apachegeod...@gmail.com wrote: Pipeline results can be found a

Geode unit tests 'develop/DistributedTest' took too long to execute

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