Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/15

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

2017-12-06 Thread Apache Jenkins Server
See Changes: [nabarunnag] GEODE-4042: Cargo tests will use java.io.tmpdir if possible, instead [github] GEODE-4035: Refactor Converter classes (#1110) [github] GEODE-4029: Deployed jars may not be correct wh

Build failed in Jenkins: Geode-nightly #1035

2017-12-06 Thread Apache Jenkins Server
See Changes: [jinmeiliao] GEODE-4049: add convenience methods for easy mocking and reduce code [jinmeiliao] GEODE-4049: add convenience methods for easy mocking and reduce code [jinmeiliao] GEODE-4049: refactor

Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/14

Re: Has github changed some preferences?

2017-12-06 Thread Jacob Barrett
Yes, something changed on GH very recently. My previous PR a few days ago was correct by default. Today I had to explicitly select develop branch. > On Dec 6, 2017, at 3:57 PM, Dave Barnes wrote: > > I was bitten by that earlier this afternoon. Instead of 2 files modified in > 1 commit, I had

Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/17

Please remember to prune your branches from the GitHub repository.

2017-12-06 Thread Patrick Rhomberg
Hello all. There are currently 80+ branches in the apache/geode.git GitHub that have not been touched in over three months. Most of these are feature/ branches, may of which have been merged. If you use the apache/geode.git repository for development of your pull requests, please be sure to c

Re: Has github changed some preferences?

2017-12-06 Thread Dave Barnes
I was bitten by that earlier this afternoon. Instead of 2 files modified in 1 commit, I had 5,000 commits! On Wed, Dec 6, 2017 at 3:52 PM, Jens Deppe wrote: > It seems that (at least my github pages) are acting a bit differently. > > When creating a Pull Request make sure that you create it agai

Has github changed some preferences?

2017-12-06 Thread Jens Deppe
It seems that (at least my github pages) are acting a bit differently. When creating a Pull Request make sure that you create it against *develop* and not *master*: [image: Inline image 1] I would typically just ignore this and click through but that led me to creating a PR with 100s of changes.

Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/13

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

2017-12-06 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #758 was successful. --- Scheduled 2266 tests in total. https://build.spring.io/browse/SGF-NAG-758/ -- This

Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/15

Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/14

Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/14

Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/15

Re: [DISCUSS] Proposal to Deprecate Hash Index

2017-12-06 Thread Bruce Schuchardt
+1 On 12/6/17 9:41 AM, Barry Oglesby wrote: +1 Thanks, Barry Oglesby On Tue, Dec 5, 2017 at 9:47 PM, Kirk Lund wrote: +1 On Tue, Dec 5, 2017 at 4:34 PM, Dan Smith wrote: +1 -Dan On Tue, Dec 5, 2017 at 4:28 PM, Jason Huynh wrote: This is a proposal to deprecate existing Hash Index

Re: [DISCUSS] Proposal to Deprecate Hash Index

2017-12-06 Thread Barry Oglesby
+1 Thanks, Barry Oglesby On Tue, Dec 5, 2017 at 9:47 PM, Kirk Lund wrote: > +1 > > On Tue, Dec 5, 2017 at 4:34 PM, Dan Smith wrote: > > > +1 > > > > -Dan > > > > On Tue, Dec 5, 2017 at 4:28 PM, Jason Huynh wrote: > > > > > This is a proposal to deprecate existing Hash Index and deprecate the

Geode tests completed in pipeline with non-zero exit code

2017-12-06 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/12