Geode tests completed in pipeline with non-zero exit code

[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

[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 when multiple locators a…

[github] GEODE-4033: Exception is thrown when Tx Id is not found on server dur…

[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 CreateRegionCommand and DestoryRegionCommand 
status

[nabarunnag] GEODE-4042: Fixed additional tmp dir references (#1121)

[bschuchardt] GEODE-3683 CacheConnectionTimeoutJUnitTest failing intermittently 
in CI

[bschuchardt] GEODE-3923 Provide whitelist/blacklist capability for java 
serialization

[dsmith] GEODE-4058: Always delete disk files after every test runs

[github] GEODE-4052: Extract GfshExitCodeStatusCommandsTest to multiple

[prhomberg] GEODE-3955: Preparing, refactoring, and addition of test utility

[prhomberg] GEODE-3955: Add AEQ and Gateway Sender information to 'describe 
region'

[dsmith] GEODE-4007: Authentication/Handshake errors should close the socket

[dsmith] GEODE-4053: Create module for Protobuf messages

--
[...truncated 110.67 KB...]
:geode-lucene:classes
:geode-old-client-support:compileJavaNote: Some input files use or override a 
deprecated API.
Note: Recompile with -Xlint:deprecation for details.

:geode-old-client-support:processResources
:geode-old-client-support:classes
:geode-protobuf-messages:extractIncludeProto
:geode-protobuf-messages:extractProto
:geode-protobuf-messages:generateProto
Download 
https://repo1.maven.org/maven2/com/google/protobuf/protoc/3.0.0/protoc-3.0.0.pom
Download 
https://repo1.maven.org/maven2/com/google/protobuf/protoc/3.0.0/protoc-3.0.0-linux-x86_64.exe
:geode-protobuf-messages:compileJava
:geode-protobuf-messages:processResources
:geode-protobuf-messages:classes
:geode-protobuf-messages:jar
:geode-protobuf:compileJavaNote: Some input files use unchecked or unsafe 
operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-protobuf:processResources
:geode-protobuf:classes
:geode-pulse:compileJava
Download 
https://repo1.maven.org/maven2/org/springframework/security/spring-security-config/4.2.1.RELEASE/spring-security-config-4.2.1.RELEASE.pom
Download 
https://repo1.maven.org/maven2/org/springframework/security/spring-security-ldap/4.2.1.RELEASE/spring-security-ldap-4.2.1.RELEASE.pom
Download 
https://repo1.maven.org/maven2/org/springframework/security/spring-security-web/4.2.1.RELEASE/spring-security-web-4.2.1.RELEASE.pom
Download 
https://repo1.maven.org/maven2/org/springframework/spring-tx/4.3.6.RELEASE/spring-tx-4.3.6.RELEASE.pom
Download 
https://repo1.maven.org/maven2/org/springframework/security/spring-security-core/4.2.1.RELEASE/spring-security-core-4.2.1.RELEASE.pom
Download 
https://repo1.maven.org/maven2/org/springframework/security/spring-security-config/4.2.1.RELEASE/spring-security-config-4.2.1.RELEASE.jar
Download 
https://repo1.maven.org/maven2/org/springframework/security/spring-security-ldap/4.2.1.RELEASE/spring-security-ldap-4.2.1.RELEASE.jar
Download 
https://repo1.maven.org/maven2/org/springframework/security/spring-security-web/4.2.1.RELEASE/spring-security-web-4.2.1.RELEASE.jar
Download 
https://repo1.maven.org/maven2/org/springframework/spring-tx/4.3.6.RELEASE/spring-tx-4.3.6.RELEASE.jar
Download 
https://repo1.maven.org/maven2/org/springframework/security/spring-security-core/4.2.1.RELEASE/spring-security-core-4.2.1.RELEASE.jar
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:geode-pulse:copyGemFireVersionFile
:geode-pulse:processResources
:geode-pulse:classes
:geode-rebalancer:compileJavaNote: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

:geode-rebalancer:processResources NO-SOURCE
:geode-rebalancer:classes
:geode-wan:compileJavaNote: 

 uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

:geode-wan:processResources
:geode-wan:classes
:geode-web:compileJava NO-SOURCE
:geode-web:processResources NO-SOURCE
:geode-web:classes UP-TO-DATE
:geode-web-api:compileJava
Download 
https://repo1.maven.org/maven2/com/fasterxml/jackson/module/jackson-module-scala_2.10/2.8.6/jackson-module-scala_2.10-2.8.6.pom
Download 

Build failed in Jenkins: Geode-nightly #1035

[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 CreateRegionCommand and DestoryRegionCommand 
status

[nabarunnag] GEODE-4042: Fixed additional tmp dir references (#1121)

[bschuchardt] GEODE-3683 CacheConnectionTimeoutJUnitTest failing intermittently 
in CI

--
[...truncated 116.92 KB...]

org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest > 
onlineStatusCommandShouldSucceedWhenConnected_server_name FAILED
org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitLoudly(GfshScript.java:141)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:112)
at 
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:94)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:105)
at 
org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest$TestConfiguration.startNecessaryMembers(GfshExitCodeStatusCommandsTest.java:397)
at 
org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest.onlineStatusCommandShouldSucceedWhenConnected_server_name(GfshExitCodeStatusCommandsTest.java:161)

org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest > 
onlineStatusCommandShouldFailWhenNotConnected_locator_name FAILED
org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitLoudly(GfshScript.java:141)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:112)
at 
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:94)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:105)
at 
org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest$TestConfiguration.startNecessaryMembers(GfshExitCodeStatusCommandsTest.java:397)
at 
org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest.onlineStatusCommandShouldFailWhenNotConnected_locator_name(GfshExitCodeStatusCommandsTest.java:109)

org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest > 
onlineStatusCommandShouldFailWhenConnectedNonDefaultPort_locator_host FAILED
org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitLoudly(GfshScript.java:141)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:112)
at 
org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:94)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.execute(GfshScript.java:105)
at 
org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest$TestConfiguration.startNecessaryMembers(GfshExitCodeStatusCommandsTest.java:397)
at 
org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest.onlineStatusCommandShouldFailWhenConnectedNonDefaultPort_locator_host(GfshExitCodeStatusCommandsTest.java:188)

org.apache.geode.management.internal.cli.shell.GfshExitCodeStatusCommandsTest > 
statusCommandWithValidOptionValueShouldFailWithNoMembers(status locator 
--port=10334) [1] FAILED
org.junit.ComparisonFailure: expected:<[1]> but was:<[0]>
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:116)

Geode tests completed in pipeline with non-zero exit code

[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?

[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 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 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.
>> 
>> I'll be double-checking for the next PR...
>> 
>> --Jens
>> 

Geode tests completed in pipeline with non-zero exit code

[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.

[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 clean up after yourself.  Alternatively, if you
fork the apache/geode.git, your branches won't clutter the common area, as
it were.
  Thanks.

Imagination is Change.
~Patrick Rhomberg

Re: Has github changed some preferences?

[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 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.
>
> I'll be double-checking for the next PR...
>
> --Jens
>

Has github changed some preferences?

[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.

I'll be double-checking for the next PR...

--Jens

Geode tests completed in pipeline with non-zero exit code

[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)

[Spring CI]

---
Spring Data GemFire > Nightly-ApacheGeode > #758 was successful.
---
Scheduled
2266 tests in total.

https://build.spring.io/browse/SGF-NAG-758/





--
This message is automatically generated by Atlassian Bamboo

Geode tests completed in pipeline with non-zero exit code

[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

[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

[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

[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

[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 and deprecate the
create hash index apis.


Currently the Hash Index name causes confusion. It is not a traditional
hash look up index, but more of memory savings index.  The index does

not

store index keys in memory and must hash the keys every time.  The

index

synchronizes on a backing array and when the backing array needs to be
expanded, it currently needs to rehash all elements in the array.  This

can

be very problematic for larger data sets.


There were improvements made to one of the functional indexes (compact
range index) prior to open sourcing.  These improvements helped reduce

the

memory consumption of that index and makes it very similar sized to a

hash

index, but the keys still are stored in memory.  Probably close enough

to

be a replacement for the hash index in most cases.  The read/write
performance on it is also faster than the hash index.


If anyone has any objections, please let us know and why.


Thanks,

- Jason

Re: [DISCUSS] Proposal to Deprecate Hash Index

[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
> > > create hash index apis.
> > >
> > >
> > > Currently the Hash Index name causes confusion. It is not a traditional
> > > hash look up index, but more of memory savings index.  The index does
> not
> > > store index keys in memory and must hash the keys every time.  The
> index
> > > synchronizes on a backing array and when the backing array needs to be
> > > expanded, it currently needs to rehash all elements in the array.  This
> > can
> > > be very problematic for larger data sets.
> > >
> > >
> > > There were improvements made to one of the functional indexes (compact
> > > range index) prior to open sourcing.  These improvements helped reduce
> > the
> > > memory consumption of that index and makes it very similar sized to a
> > hash
> > > index, but the keys still are stored in memory.  Probably close enough
> to
> > > be a replacement for the hash index in most cases.  The read/write
> > > performance on it is also faster than the hash index.
> > >
> > >
> > > If anyone has any objections, please let us know and why.
> > >
> > >
> > > Thanks,
> > >
> > > - Jason
> > >
> >
>

Geode tests completed in pipeline with non-zero exit code

[apachegeodeci]

Pipeline results can be found at:

Concourse: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/12