[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #453 has FAILED (11 tests failed, no failures were new)

2017-01-28 Thread Spring CI 

---
Spring Data GemFire > Nightly-ApacheGeode > #453 failed.
---
Scheduled
11/1666 tests failed, no failures were new.

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

-
Currently Responsible
-

John Blum 



--
Failing Jobs
--
  - Default Job (Default Stage): 11 of 1666 tests failed.




--
Tests
--
Existing Test Failures (11)
   - ClientSubRegionTest: Org.springframework.data.gemfire.client. client sub 
region test
   - GemFireDataSourceTest: Org.springframework.data.gemfire.client. gem fire 
data source test
   - GemFireDataSourceWithLocalRegionTest: 
Org.springframework.data.gemfire.client. gem fire data source with local region 
test
   - ContinuousQueryListenerContainerNamespaceTest: 
Org.springframework.data.gemfire.config.xml. continuous query listener 
container namespace test
   - ClientCacheFunctionExecutionWithPdxIntegrationTest: 
Org.springframework.data.gemfire.function. client cache function execution with 
pdx integration test
   - FunctionExecutionTests: 
Org.springframework.data.gemfire.function.execution. function execution tests
   - FunctionIntegrationTests: 
Org.springframework.data.gemfire.function.execution. function integration tests
   - GemfireFunctionTemplateTests: 
Org.springframework.data.gemfire.function.execution. gemfire function template 
tests
   - ListenerContainerTests: Org.springframework.data.gemfire.listener. 
listener container tests
   - ContainerXmlSetupTest: Org.springframework.data.gemfire.listener.adapter. 
container xml setup test
   - RepositoryClientRegionTests: 
Org.springframework.data.gemfire.repository.config. repository client region 
tests

--
This message is automatically generated by Atlassian Bamboo

Fwd: Build failed in Jenkins: Geode-release #39

2017-01-28 Thread Anthony Baker 
Looks like some lucene tests are failing on the release branch.

Anthony


> Begin forwarded message:
> 
> From: Apache Jenkins Server 
> Subject: Build failed in Jenkins: Geode-release #39
> Date: January 27, 2017 at 11:01:59 PM PST
> To: dev@geode.apache.org
> Reply-To: dev@geode.apache.org
> 
> See 
> 
> --
> [...truncated 1038 lines...]
> :geode-cq:spotlessCheck
> :geode-cq:test
> :geode-cq:check
> :geode-cq:build
> :geode-cq:distributedTest
> :geode-cq:flakyTest
> :geode-cq:integrationTest
> :geode-json:assemble
> :geode-json:compileTestJava UP-TO-DATE
> :geode-json:processTestResources UP-TO-DATE
> :geode-json:testClasses UP-TO-DATE
> :geode-json:checkMissedTests UP-TO-DATE
> :geode-json:spotlessJavaCheck
> :geode-json:spotlessCheck
> :geode-json:test UP-TO-DATE
> :geode-json:check
> :geode-json:build
> :geode-json:distributedTest UP-TO-DATE
> :geode-json:flakyTest UP-TO-DATE
> :geode-json:integrationTest UP-TO-DATE
> :geode-junit:javadoc
> :geode-junit:javadocJar
> :geode-junit:sourcesJar
> :geode-junit:signArchives SKIPPED
> :geode-junit:assemble
> :geode-junit:compileTestJava
> :geode-junit:processTestResources UP-TO-DATE
> :geode-junit:testClasses
> :geode-junit:checkMissedTests
> :geode-junit:spotlessJavaCheck
> :geode-junit:spotlessCheck
> :geode-junit:test
> :geode-junit:check
> :geode-junit:build
> :geode-junit:distributedTest
> :geode-junit:flakyTest
> :geode-junit:integrationTest
> :geode-lucene:assemble
> :geode-lucene:compileTestJava
> Download 
> https://repo1.maven.org/maven2/org/apache/lucene/lucene-test-framework/6.0.0/lucene-test-framework-6.0.0.pom
> Download 
> https://repo1.maven.org/maven2/org/apache/lucene/lucene-codecs/6.0.0/lucene-codecs-6.0.0.pom
> Download 
> https://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/randomizedtesting-runner/2.3.2/randomizedtesting-runner-2.3.2.pom
> Download 
> https://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/randomizedtesting-parent/2.3.2/randomizedtesting-parent-2.3.2.pom
> Download 
> https://repo1.maven.org/maven2/org/apache/lucene/lucene-test-framework/6.0.0/lucene-test-framework-6.0.0.jar
> Download 
> https://repo1.maven.org/maven2/org/apache/lucene/lucene-codecs/6.0.0/lucene-codecs-6.0.0.jar
> Download 
> https://repo1.maven.org/maven2/com/carrotsearch/randomizedtesting/randomizedtesting-runner/2.3.2/randomizedtesting-runner-2.3.2.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-lucene:processTestResources
> :geode-lucene:testClasses
> :geode-lucene:checkMissedTests
> :geode-lucene:spotlessJavaCheck
> :geode-lucene:spotlessCheck
> :geode-lucene:test
> :geode-lucene:check
> :geode-lucene:build
> :geode-lucene:distributedTest
> 
> org.apache.geode.cache.lucene.LuceneQueriesPeerFixedPRDUnitTest > 
> returnCorrectResultsWhenBucketIsMovedAndMovedBackOnIndexUpdate FAILED
>java.lang.AssertionError
> 
> org.apache.geode.cache.lucene.internal.management.LuceneManagementDUnitTest > 
> classMethod FAILED
>java.lang.RuntimeException: Unable to launch dunit VMs
> 
>Caused by:
>java.lang.RuntimeException: VMs did not start up within 120 seconds
> 
> org.apache.geode.cache.lucene.LuceneIndexCreationOnFixedPRDUnitTest > 
> classMethod FAILED
>java.lang.RuntimeException: Unable to launch dunit VMs
> 
>Caused by:
>java.lang.RuntimeException: VMs did not start up within 120 seconds
> 
> org.apache.geode.cache.lucene.LuceneQueriesPeerPRRedundancyDUnitTest > 
> classMethod FAILED
>java.lang.RuntimeException: Unable to launch dunit VMs
> 
>Caused by:
>java.lang.RuntimeException: VMs did not start up within 120 seconds
> 
> org.apache.geode.cache.lucene.LuceneQueriesPeerPRDUnitTest > classMethod 
> FAILED
>java.lang.RuntimeException: Unable to launch dunit VMs
> 
>Caused by:
>java.lang.RuntimeException: VMs did not start up within 120 seconds
> 
> 86 tests completed, 5 failed
> :geode-lucene:distributedTest FAILED
> :geode-lucene:flakyTest
> :geode-lucene:integrationTest
> :geode-old-client-support:assemble
> :geode-old-client-support:compileTestJava
> :geode-old-client-support:processTestResources UP-TO-DATE
> :geode-old-client-support:testClasses
> :geode-old-client-support:checkMissedTests
> :geode-old-client-support:spotlessJavaCheck
> :geode-old-client-support:spotlessCheck
> :geode-old-client-support:test
> :geode-old-client-support:check
> :geode-old-client-support:build
> :geode-old-client-support:distributedTest
> :geode-old-client-support:flakyTest
> :geode-old-client-support:integrationTest
> :geode-old-versions:javadoc UP-TO-DATE
> :geode-old-versions:javadocJar
> :geode-old-versions:sourcesJar
> :geode-old-versions:signArchives

Re: The next release (v1.1.0)

2017-01-28 Thread Michael Stolz 
Yay!
+1

--
Mike Stolz
Principal Engineer, GemFire Product Manager
Mobile: 631-835-4771

On Fri, Jan 27, 2017 at 6:40 AM, Anthony Baker  wrote:

> Looks like all the JIRA’s for v1.1.0  have been wrapped up [1].  I say
> let’s cut a release branch and move ahead.
>
> Anthony
>
> [1] https://issues.apache.org/jira/browse/GEODE/fixforversion/12338352/?
> selectedTab=com.atlassian.jira.jira-projects-plugin:version-summary-panel
>
> > On Jan 24, 2017, at 1:14 PM, Mark Bretl  wrote:
> >
> > Do we think we can get these done and get a release before the next board
> > meeting (2/15)? I think it would be an excellent point on our report.
> >
> > Best Regards,
> >
> > --Mark
> >
> > On Tue, Jan 24, 2017 at 12:09 PM, Hitesh Khamesra <
> > hitesh...@yahoo.com.invalid> wrote:
> >
> >> Update: Three more ticket for first release candidate..
> >>
> >> GEODE-2300 Document default names for start locator/server
> >> GEODE-2353 Verify no clear-text passwords in documentation
> >> GEODE-2282 Provide ability to sort field while creating pdxType for jSON
> >> document(Need to document system property)
> >>
> >> Thanks.HItesh
> >>
> >>
> >>
> >>  From: Hitesh Khamesra 
> >> To: "dev@geode.apache.org" 
> >> Sent: Monday, January 16, 2017 12:35 PM
> >> Subject: Re: The next release (v1.1.0)
> >>
> >> Update: We are waiting on following tickets for first release candidate.
> >>
> >> 1.  GEODE-2296 GetFunctionAttribute command is throwing an Anonymouse
> User
> >> Exception
> >> 2.  GEODE-2277 client cache fails to deserialize a PdxInstance due to
> >> InternalGemFireError
> >> 3.  GEODE-2031 Host documentation for releases
> >> 4.  GEODE-1965 Create backward-compatibility unit test framework
> >>
> >> Thanks.HItesh
> >>
> >>  From: Anthony Baker 
> >> To: dev@geode.apache.org
> >> Sent: Monday, January 9, 2017 9:49 AM
> >> Subject: Re: The next release (v1.1.0)
> >>
> >> Updates:
> >>
> >> 1) I did a first round of changes on GEODE-2142, should be enough for
> >> v1.1.0.
> >> 2) Any volunteers to look at GEODE-2031 or GEODE-1965?
> >> 3) Are there other open issues that should be included in the release?
> >> 4) Last call for a release manager…  :-)
> >>
> >> Thanks,
> >> Anthony
> >>
> >>
> >>> On Jan 6, 2017, at 10:13 AM, Anthony Baker  wrote:
> >>>
> >>> Our last release was on October 25.  I think we’re past due for another
> >> one!  We’ve had lots of great contributions since 1.0.0-incubating and
> now
> >> that we’re are a top-level project we can drop the “-incubating”
> qualifier.
> >>>
> >>> I reviewed our open JIRA issues and would like to include the following
> >> in the release:
> >>>
> >>> GEODE-2142 - JSON license incompatibility
> >>>We can update the NOTICE files and leave the JSON dependency alone
> >> (as long as we do another release before April 30).
> >>>
> >>> GEODE-1965 - backwards compatibility tests
> >>>I’d like to make sure we haven’t broken anything since our last
> >> release.
> >>>
> >>> GEODE-2031 - versioned documentation
> >>>Seems relatively straightforward?
> >>>
> >>> The remaining issues that are tagged with v1.1.0 [1] could be pushed to
> >> a following release IMO.  Thoughts?
> >>>
> >>> Regarding the release manager, I can do the dirty work if no one else
> >> wants to volunteer :-)
> >>>
> >>> Anthony
> >>>
> >>> [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20G
> >> EODE%20AND%20fixVersion%20%3D%201.1.0%20AND%20resolution%20%
> >> 3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%
> >> 20DESC%2C%20created%20ASC
> >>>
>  On Nov 21, 2016, at 9:26 AM, Anthony Baker  wrote:
> 
>  Now that graduation is done (!!), we need to organize our next
> >> release.  I propose we focus on completing the transition to TLP and
> >> cleaning up “incubating" references.  The sequence would look something
> >> like this:
> 
>  1) Transition the git repo, mailing lists, etc.
>  2) Update incubating references in source, docs, website, wiki, …
>  3) Do a release.
> 
>  Thoughts?
> 
>  We need a release manager.  Any volunteers?
> 
>  Also, we need to rename the JIRA version from 1.1.0-incubating to
> >> 1.1.0.  Can someone with JIRA karma help?
> 
>  Anthony
> 
> >>>
> >>
> >>
> >>
> >>
> >>
> >>
>
>

[GitHub] geode pull request #370: Feature/geode 2351

2017-01-28 Thread mmartell 
GitHub user mmartell opened a pull request:

https://github.com/apache/geode/pull/370

Feature/geode 2351



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mmartell/geode feature/GEODE-2351

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/geode/pull/370.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #370


commit 2aff17552a670c26c2c386866462f00605213b86
Author: Mike Martell 
Date:   2017-01-28T16:52:03Z

GEODE-2351: Fix for clang-format arg limit on Windows.

commit d0e68c241cfdd7bae90bb9a438600471737ad4f9
Author: Mike Martell 
Date:   2017-01-28T16:52:27Z

GEODE-2351: Replace gemfire with geode in cpp quickstarts.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Build failed in Jenkins: Geode-nightly #730

2017-01-28 Thread Apache Jenkins Server 
See 

Changes:

[hkhamesra] updated version number to 1.2.0 in gradle.properties.

[kduling] GEODE-2298: Executing a Function via Swagger without parameters throws

[kduling] GEODE-2294: When attempting to execute a function via Dev Rest API,

[huynhja] GEODE-2367: Lucene indexes do not handle ha scenarios

--
[...truncated 574 lines...]
:geode-json:flakyTest UP-TO-DATE
:geode-json:integrationTest UP-TO-DATE
:geode-junit:javadoc
:geode-junit:javadocJar
:geode-junit:sourcesJar
:geode-junit:signArchives SKIPPED
:geode-junit:assemble
:geode-junit:compileTestJava
:geode-junit:processTestResources UP-TO-DATE
:geode-junit:testClasses
:geode-junit:checkMissedTests
:geode-junit:spotlessJavaCheck
:geode-junit:spotlessCheck
:geode-junit:test
:geode-junit:check
:geode-junit:build
:geode-junit:distributedTest
:geode-junit:flakyTest
:geode-junit:integrationTest
:geode-lucene:assemble
:geode-lucene:compileTestJavaNote: 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-lucene:processTestResources
:geode-lucene:testClasses
:geode-lucene:checkMissedTests
:geode-lucene:spotlessJavaCheck
:geode-lucene:spotlessCheck
:geode-lucene:test
:geode-lucene:check
:geode-lucene:build
:geode-lucene:distributedTest

org.apache.geode.cache.lucene.LuceneQueriesPeerPROverflowDUnitTest > 
defaultFieldShouldPropogateCorrectlyThroughFunction FAILED
org.apache.geode.test.dunit.RMIException: While invoking 
org.apache.geode.cache.lucene.LuceneQueriesBase$$Lambda$26/1017789008.run in VM 
3 running on Host asf920.gq1.ygridcore.net with 4 VMs

Caused by:
java.lang.AssertionError: expected:<3> but was:<5>

140 tests completed, 1 failed
:geode-lucene:distributedTest FAILED
:geode-lucene:flakyTest
:geode-lucene:integrationTest
:geode-old-client-support:assemble
:geode-old-client-support:compileTestJava
:geode-old-client-support:processTestResources UP-TO-DATE
:geode-old-client-support:testClasses
:geode-old-client-support:checkMissedTests
:geode-old-client-support:spotlessJavaCheck
:geode-old-client-support:spotlessCheck
:geode-old-client-support:test
:geode-old-client-support:check
:geode-old-client-support:build
:geode-old-client-support:distributedTest
:geode-old-client-support:flakyTest
:geode-old-client-support:integrationTest
:geode-old-versions:javadoc UP-TO-DATE
:geode-old-versions:javadocJar
:geode-old-versions:sourcesJar
:geode-old-versions:signArchives SKIPPED
:geode-old-versions:assemble
:geode-old-versions:compileTestJava UP-TO-DATE
:geode-old-versions:processTestResources UP-TO-DATE
:geode-old-versions:testClasses UP-TO-DATE
:geode-old-versions:checkMissedTests UP-TO-DATE
:geode-old-versions:spotlessJavaCheck
:geode-old-versions:spotlessCheck
:geode-old-versions:test UP-TO-DATE
:geode-old-versions:check
:geode-old-versions:build
:geode-old-versions:distributedTest UP-TO-DATE
:geode-old-versions:flakyTest UP-TO-DATE
:geode-old-versions:integrationTest UP-TO-DATE
:geode-pulse:assemble
:geode-pulse:compileTestJavaNote: 

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

 uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

:geode-pulse:processTestResources
:geode-pulse:testClasses
:geode-pulse:checkMissedTests
:geode-pulse:spotlessJavaCheck
:geode-pulse:spotlessCheck
:geode-pulse:test
:geode-pulse:check
:geode-pulse:build
:geode-pulse:distributedTest
:geode-pulse:flakyTest
:geode-pulse:integrationTest
:geode-rebalancer:assemble
:geode-rebalancer:compileTestJava
:geode-rebalancer:processTestResources UP-TO-DATE
:geode-rebalancer:testClasses
:geode-rebalancer:checkMissedTests
:geode-rebalancer:spotlessJavaCheck
:geode-rebalancer:spotlessCheck
:geode-rebalancer:test
:geode-rebalancer:check
:geode-rebalancer:build
:geode-rebalancer:distributedTest
:geode-rebalancer:flakyTest
:geode-rebalancer:integrationTest
:geode-wan:assemble
:geode-wan:compileTestJavaNote: 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-wan:processTestResources
:geode-wan:testClasses
:geode-wan:checkMissedTests
:geode-wan:spotlessJavaCheck
:geode-wan:spotlessCheck
:geode-wan:test
:geode-wan:check
:geode-wan:build
:geode-wan:distributedTest
:geode-wan:flakyTest
:geode-wan:integrationTest
:geode-web:assemble
:geode-web:compileTestJavaNote: Some input files use or

[jira] [Commented] (GEODE-2370) Need to create a CONTRIBUTING.md

2017-01-28 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/GEODE-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15844073#comment-15844073
 ] 

ASF GitHub Bot commented on GEODE-2370:
---

Github user pivotal-jbarrett commented on the issue:

https://github.com/apache/geode/pull/367
  
We should include links to CTest documents.

To run singles or subsets of tests you need to use ctest directly. 

ctest -R 




> Need to create a CONTRIBUTING.md
> 
>
> Key: GEODE-2370
> URL: https://issues.apache.org/jira/browse/GEODE-2370
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Ernest Burghardt
>
> The community will be contributing and will want some basic instruction as to 
> how this is done and expectations...
> i.e. the expectation to submit properly formatted code; we need to create a  
> CONTRIBUTING.md that among other items it might cover,  should show how to 
> apply the formatting using the "format" target for c++ code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] geode issue #367: GEODE-2370: First pass at a CONTRIBUTING document.

2017-01-28 Thread pivotal-jbarrett 
Github user pivotal-jbarrett commented on the issue:

https://github.com/apache/geode/pull/367
  
We should include links to CTest documents.

To run singles or subsets of tests you need to use ctest directly. 

ctest -R 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---