Last call on 1.2.0 (and fixing test failures)

Hi everyone, Our last release was v1.1.1 in March. We have made a lot of great progress on the develop branch with over 250 issues fixed. It would be great to get those changes into a release. What’s left before we are ready to release 1.2.0? Note that we need a clean test run before

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #554 has FAILED

--- Spring Data GemFire > Nightly-ApacheGeode > #554 failed. --- Scheduled No failed tests found, a possible compilation error.

[GitHub] geode pull request #514: GEODE-2905: Added extra logging to determine the ca...

GitHub user nabarunnag opened a pull request: https://github.com/apache/geode/pull/514 GEODE-2905: Added extra logging to determine the cause of failure. * Replaced assertTrue with assertEquals so that the commandResult is displayed in case of an error. Thank you for

[jira] [Commented] (GEODE-2905) CI failure: org.apache.geode.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest > searchWithoutIndexShouldReturnError

[ https://issues.apache.org/jira/browse/GEODE-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009811#comment-16009811 ] ASF GitHub Bot commented on GEODE-2905: --- GitHub user nabarunnag opened a pull request:

[jira] [Resolved] (GEODE-2637) LuceneQueryFactory.setResultLimit() method should match LuceneQuery.getLimit()

[ https://issues.apache.org/jira/browse/GEODE-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nabarun resolved GEODE-2637. Resolution: Fixed Fix Version/s: 1.2.0 > LuceneQueryFactory.setResultLimit() method should match

Build failed in Jenkins: Geode-nightly #835

See -- [...truncated 106.83 KB...] 6858 tests completed, 7 failed, 604 skipped :geode-core:distributedTest FAILED :geode-core:flakyTest :geode-core:integrationTest :geode-cq:assemble

[jira] [Commented] (GEODE-2891) connect-timeout violation in C++ Native Client

[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16009660#comment-16009660 ] Gregory Vortman commented on GEODE-2891: Thanks Jacob. It was my bad. I fixed the attachment and

[jira] [Reopened] (GEODE-2891) connect-timeout violation in C++ Native Client

[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Vortman reopened GEODE-2891: > connect-timeout violation in C++ Native Client >

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Vortman updated GEODE-2891: --- Attachment: GEODE-connect-timeout-violation.docx > connect-timeout violation in C++ Native

[jira] [Updated] (GEODE-2891) connect-timeout violation in C++ Native Client

[ https://issues.apache.org/jira/browse/GEODE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gregory Vortman updated GEODE-2891: --- Attachment: (was: gemfire-connect-timeout-violation.docx) > connect-timeout violation in