[jira] [Created] (GEODE-7990) Update to dependencies

2020-04-15 Thread Jacob Barrett (Jira)
Jacob Barrett created GEODE-7990:


 Summary: Update to dependencies
 Key: GEODE-7990
 URL: https://issues.apache.org/jira/browse/GEODE-7990
 Project: Geode
  Issue Type: Improvement
  Components: native client
Reporter: Jacob Barrett


Update dependencies:
* ACE 6.5.8
* SQLite 3.31.1
* Xerces-C 3.2.3




--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (GEODE-7990) Update to dependencies

2020-04-15 Thread Jacob Barrett (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jacob Barrett reassigned GEODE-7990:


Assignee: Jacob Barrett

> Update to dependencies
> --
>
> Key: GEODE-7990
> URL: https://issues.apache.org/jira/browse/GEODE-7990
> Project: Geode
>  Issue Type: Improvement
>  Components: native client
>Reporter: Jacob Barrett
>Assignee: Jacob Barrett
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Update dependencies:
> * ACE 6.5.8
> * SQLite 3.31.1
> * Xerces-C 3.2.3



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (GEODE-7870) PubSubIntegrationTest is still flaky

2020-04-15 Thread Jens Deppe (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jens Deppe resolved GEODE-7870.
---
Fix Version/s: 1.13.0
   Resolution: Fixed

> PubSubIntegrationTest is still flaky
> 
>
> Key: GEODE-7870
> URL: https://issues.apache.org/jira/browse/GEODE-7870
> Project: Geode
>  Issue Type: Bug
>  Components: redis
>Reporter: Jens Deppe
>Priority: Major
> Fix For: 1.13.0
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> This test still fails intermittently (but much less than it used to be).
> Here is an example failure:
> {noformat}
> org.apache.geode.redis.PubSubIntegrationTest > testPatternSubscribe FAILED
> java.lang.AssertionError: 
> Expecting:
>   <["hello"]>
> to contain exactly (and in same order):
>   <["hello"]>
> but could not find the following elements:
>   <["hello"]>
> at 
> org.apache.geode.redis.PubSubIntegrationTest.testPatternSubscribe(PubSubIntegrationTest.java:254)
> org.apache.geode.redis.PubSubIntegrationTest > testPatternWithoutAGlob FAILED
> org.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in org.apache.geode.redis.PubSubIntegrationTest that uses 
> org.apache.geode.redis.mocks.MockSubscriber was not fulfilled within 300 
> seconds.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860)
> at 
> org.apache.geode.redis.PubSubIntegrationTest.waitFor(PubSubIntegrationTest.java:324)
> at 
> org.apache.geode.redis.PubSubIntegrationTest.testPatternWithoutAGlob(PubSubIntegrationTest.java:301)
> org.apache.geode.redis.PubSubIntegrationTest > testTwoSubscribersOneChannel 
> FAILED
> org.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in org.apache.geode.redis.PubSubIntegrationTest that uses 
> org.apache.geode.redis.mocks.MockSubscriber was not fulfilled within 300 
> seconds.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860)
> at 
> org.apache.geode.redis.PubSubIntegrationTest.waitFor(PubSubIntegrationTest.java:324)
> at 
> org.apache.geode.redis.PubSubIntegrationTest.testTwoSubscribersOneChannel(PubSubIntegrationTest.java:166)
> org.apache.geode.redis.PubSubIntegrationTest > 
> testOneSubscriberSubscribingToTwoChannels FAILED
> org.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in org.apache.geode.redis.PubSubIntegrationTest that uses 
> org.apache.geode.redis.mocks.MockSubscriber was not fulfilled within 300 
> seconds.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860)
> at 
> org.apache.geode.redis.PubSubIntegrationTest.waitFor(PubSubIntegrationTest.java:324)
> at 
> org.apache.geode.redis.PubSubIntegrationTest.testOneSubscriberSubscribingToTwoChannels(PubSubIntegrationTest.java:136)
> org.apache.geode.redis.PubSubIntegrationTest > testPatternAndRegularSubscribe 
> FAILED
> org.awaitility.core.ConditionTimeoutException: Condition with lambda 
> expression in org.apache.geode.redis.PubSubIntegrationTest that uses 
> org.apache.geode.redis.mocks.MockSubscriber was not fulfilled within 300 
> seconds.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:79)
> at 
> org.awaitility.core.CallableCondition.await(CallableCondition.java:27)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:860)
> at 
> org.apache.geode.redis.PubSubIntegrationTest.waitFor(PubSubIntegrationTest.java:324)
> a

[jira] [Commented] (GEODE-7710) JMXMBeanReconnectDUnitTest fails intermittently because one locator is missing the LockServiceMXBean

2020-04-15 Thread Eric Shu (Jira)


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

Eric Shu commented on GEODE-7710:
-

Another CI failure: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/62#A

> JMXMBeanReconnectDUnitTest fails intermittently because one locator is 
> missing the LockServiceMXBean
> 
>
> Key: GEODE-7710
> URL: https://issues.apache.org/jira/browse/GEODE-7710
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Kirk Lund
>Assignee: Kirk Lund
>Priority: Major
>  Labels: flaky
>  Time Spent: 5h
>  Remaining Estimate: 0h
>
> Multiple tests in JMXMBeanReconnectDUnitTest may fail an await due to one of 
> the locators missing the LockServiceMXBean for the cluster config service.
> {noformat}
> but could not find:
>  
> <[GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator1]>
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7503) Creating cache after closing cache may throw DistributedSystemDisconnectedException

2020-04-15 Thread Kirk Lund (Jira)


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

Kirk Lund commented on GEODE-7503:
--

I closed the main PR (https://github.com/apache/geode/pull/4410) and this 
ticket after Anil and I discussed it further. The main concern is that the 
current behavior is expected by users and is de facto correct. Changing it 
would change the behavior and result in long-time users being surprised by the 
new behavior.

The rest of the PRs involved cleaning up GemFireCacheImpl and adding lots of 
new unit tests. Those changes were merged to develop since they didn't change 
behavior.

> Creating cache after closing cache may throw 
> DistributedSystemDisconnectedException
> ---
>
> Key: GEODE-7503
> URL: https://issues.apache.org/jira/browse/GEODE-7503
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Kirk Lund
>Priority: Major
> Fix For: 1.12.0
>
>  Time Spent: 5h
>  Remaining Estimate: 0h
>
> This problem reproduces if you attempt to create a Cache using the 
> CacheFactory immediately after closing a Cache.
> {noformat}
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This 
> connection to a distributed system has been disconnected.
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:945)
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1665)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:791)
> at 
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
> at 
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (GEODE-7991) CI Failure: ClientSNICQAcceptanceTest.performSimpleCQOverSNIProxy failed

2020-04-15 Thread Eric Shu (Jira)
Eric Shu created GEODE-7991:
---

 Summary: CI Failure: 
ClientSNICQAcceptanceTest.performSimpleCQOverSNIProxy failed
 Key: GEODE-7991
 URL: https://issues.apache.org/jira/browse/GEODE-7991
 Project: Geode
  Issue Type: Bug
  Components: membership
Reporter: Eric Shu


Failed in CI pipeline: 
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK11/builds/55#A

{noformat}
org.junit.ComparisonFailure: expected:<6[2]> but was:<6[0]>
at 
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at 
jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at 
org.apache.geode.client.sni.ClientSNICQAcceptanceTest.performSimpleCQOverSNIProxy(ClientSNICQAcceptanceTest.java:153)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58)
at 
org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38)
at 
org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:62)
at 
org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
at 
org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
at 
org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:118)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:566)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)

[jira] [Assigned] (GEODE-7934) CI Failure: CacheManagementDUnitTest

2020-04-15 Thread Ivan Godwin (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Godwin reassigned GEODE-7934:
--

Assignee: Ivan Godwin

> CI Failure: CacheManagementDUnitTest
> 
>
> Key: GEODE-7934
> URL: https://issues.apache.org/jira/browse/GEODE-7934
> Project: Geode
>  Issue Type: Bug
>Reporter: Ivan Godwin
>Assignee: Ivan Godwin
>Priority: Major
>  Labels: flaky
>
> CacheManagementDUnitTest.testNotification and 
> CacheManagementDUnitTest.testManagerShutdown have failed with the following 
> output:
>  
> {code:java}
> org.apache.geode.management.CacheManagementDUnitTest > testNotification FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 0 running 
> on Host 12ab33057072 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:424)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.verifyNotificationsAndRegionSize(CacheManagementDUnitTest.java:637)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.testNotification(CacheManagementDUnitTest.java:266)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition 
> defined as a org.apache.geode.management.CacheManagementDUnitTest 
> expected:<[45]> but was:<[30]> within 300 seconds.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at 
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.lambda$verifyNotificationsAndRegionSize$aeb9a697$1(CacheManagementDUnitTest.java:638)
> Caused by:
> org.junit.ComparisonFailure: expected:<[45]> but was:<[30]>
> at 
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.lambda$null$4(CacheManagementDUnitTest.java:638)
> {code}
>  
>  
>  
> {code:java}
> org.apache.geode.management.CacheManagementDUnitTest > testManagerShutdown 
> FAILEDorg.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 0 running 
> on Host 9e4a1b86b19b with 4 VMsat 
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)at 
> org.apache.geode.test.dunit.VM.invoke(VM.java:424)at 
> org.apache.geode.management.CacheManagementDUnitTest.verifyManagerStopped(CacheManagementDUnitTest.java:377)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.testManagerShutdown(CacheManagementDUnitTest.java:200)
> Caused by:java.lang.AssertionError: Expecting empty 
> but was:<[GemFire:type=Member,member=memberVM-3]>at 
> org.apache.geode.management.CacheManagementDUnitTest.lambda$verifyManagerStopped$36a0fae1$1(CacheManagementDUnitTest.java:391)
> {code}
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1699]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1676]
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1519
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (GEODE-7934) CI Failure: CacheManagementDUnitTest

2020-04-15 Thread Ivan Godwin (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Godwin reassigned GEODE-7934:
--

Assignee: (was: Ivan Godwin)

> CI Failure: CacheManagementDUnitTest
> 
>
> Key: GEODE-7934
> URL: https://issues.apache.org/jira/browse/GEODE-7934
> Project: Geode
>  Issue Type: Bug
>Reporter: Ivan Godwin
>Priority: Major
>  Labels: flaky
>
> CacheManagementDUnitTest.testNotification and 
> CacheManagementDUnitTest.testManagerShutdown have failed with the following 
> output:
>  
> {code:java}
> org.apache.geode.management.CacheManagementDUnitTest > testNotification FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 0 running 
> on Host 12ab33057072 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:424)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.verifyNotificationsAndRegionSize(CacheManagementDUnitTest.java:637)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.testNotification(CacheManagementDUnitTest.java:266)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Assertion condition 
> defined as a org.apache.geode.management.CacheManagementDUnitTest 
> expected:<[45]> but was:<[30]> within 300 seconds.
> at 
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:145)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:122)
> at 
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at 
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:902)
> at 
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:723)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.lambda$verifyNotificationsAndRegionSize$aeb9a697$1(CacheManagementDUnitTest.java:638)
> Caused by:
> org.junit.ComparisonFailure: expected:<[45]> but was:<[30]>
> at 
> sun.reflect.GeneratedConstructorAccessor81.newInstance(Unknown Source)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.lambda$null$4(CacheManagementDUnitTest.java:638)
> {code}
>  
>  
>  
> {code:java}
> org.apache.geode.management.CacheManagementDUnitTest > testManagerShutdown 
> FAILEDorg.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.test.dunit.internal.IdentifiableRunnable.run in VM 0 running 
> on Host 9e4a1b86b19b with 4 VMsat 
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)at 
> org.apache.geode.test.dunit.VM.invoke(VM.java:424)at 
> org.apache.geode.management.CacheManagementDUnitTest.verifyManagerStopped(CacheManagementDUnitTest.java:377)
> at 
> org.apache.geode.management.CacheManagementDUnitTest.testManagerShutdown(CacheManagementDUnitTest.java:200)
> Caused by:java.lang.AssertionError: Expecting empty 
> but was:<[GemFire:type=Member,member=memberVM-3]>at 
> org.apache.geode.management.CacheManagementDUnitTest.lambda$verifyManagerStopped$36a0fae1$1(CacheManagementDUnitTest.java:391)
> {code}
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1699]
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1676]
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1519
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (GEODE-7992) Implement a test class for the EXISTS Redis API command

2020-04-15 Thread Sarah Abbey (Jira)
Sarah Abbey created GEODE-7992:
--

 Summary: Implement a test class for the EXISTS Redis API command
 Key: GEODE-7992
 URL: https://issues.apache.org/jira/browse/GEODE-7992
 Project: Geode
  Issue Type: Test
  Components: redis, tests
Reporter: Sarah Abbey


The Redis EXISTS command verifies that a key exists 
([https://redis.io/commands/exists]).  The EXISTS command was previously 
implemented, but not tested. This PR adds tests and fixes implementation for 
this command.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (GEODE-7988) AutoConnectionSourceDUnitTest. testClientDynamicallyDropsStoppedLocator is failing in mass test run

2020-04-15 Thread Ivan Godwin (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Godwin reassigned GEODE-7988:
--

Assignee: Ivan Godwin  (was: Mark Hanson)

> AutoConnectionSourceDUnitTest. testClientDynamicallyDropsStoppedLocator is 
> failing in mass test run
> ---
>
> Key: GEODE-7988
> URL: https://issues.apache.org/jira/browse/GEODE-7988
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Affects Versions: 1.13.0
>Reporter: Mark Hanson
>Assignee: Ivan Godwin
>Priority: Major
>  Labels: flaky
>
> {noformat}
> testClientDynamicallyDropsStoppedLocator
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1993
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-mass-test-run-main/jobs/DistributedTestOpenJDK8/builds/1940
>  {noformat}
>  
> This is also reproducible using dunitrunner.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Assigned] (GEODE-7993) Gateway senders try to connect once at start up

2020-04-15 Thread Karen Smoler Miller (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller reassigned GEODE-7993:
--

Assignee: Karen Smoler Miller

> Gateway senders try to connect once at start up
> ---
>
> Key: GEODE-7993
> URL: https://issues.apache.org/jira/browse/GEODE-7993
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>
> Document that GW senders try once to connect to GW receivers upon GW sender 
> start up. If there's no receiver present at that time, it is not an error.  
> The GW sender tries again when it has a batch of events to send.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Created] (GEODE-7993) Gateway senders try to connect once at start up

2020-04-15 Thread Karen Smoler Miller (Jira)
Karen Smoler Miller created GEODE-7993:
--

 Summary: Gateway senders try to connect once at start up
 Key: GEODE-7993
 URL: https://issues.apache.org/jira/browse/GEODE-7993
 Project: Geode
  Issue Type: Improvement
  Components: docs
Reporter: Karen Smoler Miller


Document that GW senders try once to connect to GW receivers upon GW sender 
start up. If there's no receiver present at that time, it is not an error.  The 
GW sender tries again when it has a batch of events to send.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (GEODE-7460) CI failure: DistributedMemberDUnitTest.testGroupsInAllVMs ForcedDisconnectException Failure

2020-04-15 Thread Owen Nichols (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Owen Nichols updated GEODE-7460:

Fix Version/s: (was: 1.13.0)

> CI failure: DistributedMemberDUnitTest.testGroupsInAllVMs 
> ForcedDisconnectException Failure
> ---
>
> Key: GEODE-7460
> URL: https://issues.apache.org/jira/browse/GEODE-7460
> Project: Geode
>  Issue Type: Bug
>  Components: membership
>Reporter: Robert Houghton
>Assignee: Ernest Burghardt
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> From the failing job:
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0016/test-results/distributedTest/1573784422/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0016/test-artifacts/1573784422/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0016.tgz
> DistributedTest failure due to exception:
> org.apache.geode.distributed.DistributedMemberDUnitTest > testGroupsInAllVMs 
> FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.distributed.DistributedMemberDUnitTest$6.run in VM 0 running 
> on Host 3e09f1029b44 with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at 
> org.apache.geode.distributed.DistributedMemberDUnitTest.testGroupsInAllVMs(DistributedMemberDUnitTest.java:333)
> Caused by:
> org.apache.geode.SystemConnectException: One or more peers generated 
> exceptions during connection attempt
> at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendStartupMessage(ClusterDistributionManager.java:1625)
> at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.create(ClusterDistributionManager.java:354)
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.initialize(InternalDistributedSystem.java:759)
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.access$200(InternalDistributedSystem.java:136)
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem$Builder.build(InternalDistributedSystem.java:3009)
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.connectInternal(InternalDistributedSystem.java:269)
> at 
> org.apache.geode.distributed.DistributedSystem.connect(DistributedSystem.java:159)
> at 
> org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.getSystem(JUnit4DistributedTestCase.java:181)
> at 
> org.apache.geode.distributed.DistributedMemberDUnitTest$6.run(DistributedMemberDUnitTest.java:339)
> Caused by:
> 
> org.apache.geode.distributed.DistributedSystemDisconnectedException: 
> DistributedSystem is shutting down, caused by 
> org.apache.geode.ForcedDisconnectException: Exiting due to possible network 
> partition event due to loss of 1 cache processes: 
> [172.17.0.14(myName:1):41001]
> at 
> org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1591)
> at 
> org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.send(GMSMembershipManager.java:1751)
> at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2058)
> at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:1985)
> at 
> org.apache.geode.distributed.internal.StartupOperation.sendStartupMessage(StartupOperation.java:74)
> at 
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendStartupMessage(ClusterDistributionManager.java:1622)
> ... 8 more
> Caused by:
> org.apache.geode.ForcedDisconnectException: Exiting due to 
> possible network partition event due to loss of 1 cache processes: 
> [172.17.0.14(myName:1):41001]
> java.lang.AssertionError: Suspicious strings were written to the log 
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 554
> [fatal 2019/11/15 00:40:19.902 GMT  
> tid=165] Possible loss of quorum due t

[jira] [Updated] (GEODE-7503) Creating cache after closing cache may throw DistributedSystemDisconnectedException

2020-04-15 Thread Kirk Lund (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund updated GEODE-7503:
-
Fix Version/s: (was: 1.12.0)

> Creating cache after closing cache may throw 
> DistributedSystemDisconnectedException
> ---
>
> Key: GEODE-7503
> URL: https://issues.apache.org/jira/browse/GEODE-7503
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Kirk Lund
>Priority: Major
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> This problem reproduces if you attempt to create a Cache using the 
> CacheFactory immediately after closing a Cache.
> {noformat}
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This 
> connection to a distributed system has been disconnected.
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:945)
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1665)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:791)
> at 
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
> at 
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Updated] (GEODE-7503) Creating cache after closing cache may throw DistributedSystemDisconnectedException

2020-04-15 Thread Kirk Lund (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kirk Lund updated GEODE-7503:
-
Description: 
This problem is caused by a race condition and may reproduce if you attempt to 
create a Cache using the CacheFactory immediately after more than one thread 
invokes Cache.close().
{noformat}
org.apache.geode.distributed.DistributedSystemDisconnectedException: This 
connection to a distributed system has been disconnected.
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:945)
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1665)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:791)
at 
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
at 
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
{noformat}

  was:
This problem reproduces if you attempt to create a Cache using the CacheFactory 
immediately after closing a Cache.
{noformat}
org.apache.geode.distributed.DistributedSystemDisconnectedException: This 
connection to a distributed system has been disconnected.
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:945)
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1665)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:791)
at 
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
at 
org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
{noformat}


> Creating cache after closing cache may throw 
> DistributedSystemDisconnectedException
> ---
>
> Key: GEODE-7503
> URL: https://issues.apache.org/jira/browse/GEODE-7503
> Project: Geode
>  Issue Type: Bug
>  Components: core
>Reporter: Kirk Lund
>Priority: Major
>  Time Spent: 5h 10m
>  Remaining Estimate: 0h
>
> This problem is caused by a race condition and may reproduce if you attempt 
> to create a Cache using the CacheFactory immediately after more than one 
> thread invokes Cache.close().
> {noformat}
> org.apache.geode.distributed.DistributedSystemDisconnectedException: This 
> connection to a distributed system has been disconnected.
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:945)
> at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1665)
> at 
> org.apache.geode.internal.cache.GemFireCacheImpl.(GemFireCacheImpl.java:791)
> at 
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:187)
> at 
> org.apache.geode.internal.cache.InternalCacheBuilder.create(InternalCacheBuilder.java:158)
> at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:142)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Comment Edited] (GEODE-7503) Creating cache after closing cache may throw DistributedSystemDisconnectedException

2020-04-15 Thread Kirk Lund (Jira)


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

Kirk Lund edited comment on GEODE-7503 at 4/15/20, 6:02 PM:


One known cause in dunit tests is when creation of a persistent region fails 
and DiskStoreImpl.lambda$handleDiskAccessException forks a new Thread to close 
the Cache which succeeds in closing the Cache before the main test thread 
(which is invoking Cache.close()) closes it. The main test thread then 
early-outs because the DiskStore thread is already closing the Cache. The main 
test thread then tries to create a Cache which collides with the DiskStore 
thread which is still closing the Cache and is about to disconnect the 
DistributedSystem.

{noformat}
java.lang.Throwable: KIRK GemFireCacheImpl closed 632230948
at 
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2365)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1917)
at 
org.apache.geode.internal.cache.DiskStoreImpl.lambda$handleDiskAccessException$2(DiskStoreImpl.java:3380)
at java.lang.Thread.run(Thread.java:748)
{noformat}
{noformat}
java.lang.Throwable: KIRK InternalDistributedSystem closed 306674056
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1637)
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1225)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2351)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1917)
at 
org.apache.geode.internal.cache.DiskStoreImpl.lambda$handleDiskAccessException$2(DiskStoreImpl.java:3380)
at java.lang.Thread.run(Thread.java:748)
{noformat}
{noformat}
java.lang.Throwable: KIRK DiskStoreImpl closing cache 1555793073
at 
org.apache.geode.internal.cache.DiskStoreImpl.handleDiskAccessException(DiskStoreImpl.java:3376)
at 
org.apache.geode.internal.cache.PartitionedRegion.createAndValidatePersistentConfig(PartitionedRegion.java:956)
at 
org.apache.geode.internal.cache.PartitionedRegion.initPRInternals(PartitionedRegion.java:999)
at 
org.apache.geode.internal.cache.PartitionedRegion.initialize(PartitionedRegion.java:1179)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3043)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:2931)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2918)
at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:755)
at 
org.apache.geode.cache.CacheFactoryRecreateRegressionTest.createCacheAndColocatedPRs(CacheFactoryRecreateRegressionTest.java:109)
at 
org.apache.geode.cache.CacheFactoryRecreateRegressionTest.lambda$recreateDoesNotThrowDistributedSystemDisconnectedException$0(CacheFactoryRecreateRegressionTest.java:62)
at 
org.assertj.core.api.ThrowableAssert.catchThrowable(ThrowableAssert.java:62)
at 
org.assertj.core.api.AssertionsForClassTypes.catchThrowable(AssertionsForClassTypes.java:786)
at org.assertj.core.api.Assertions.catchThrowable(Assertions.java:1200)
at 
org.apache.geode.cache.CacheFactoryRecreateRegressionTest.recreateDoesNotThrowDistributedSystemDisconnectedException(CacheFactoryRecreateRegressionTest.java:62)
{noformat}


was (Author: klund):
This bug appears to be caused when creation of a persistent region fails and 
DiskStoreImpl.lambda$handleDiskAccessException forks a new Thread to close the 
Cache which succeeds in closing the Cache before the main test thread closes 
it. The main test thread then early outs because the DiskStore thread is 
already closing the Cache. The main test thread then tries to create a Cache 
which collides with the DiskStore thread which is still closing the Cache and 
DistributedSystem.

{noformat}
java.lang.Throwable: KIRK GemFireCacheImpl closed 632230948
at 
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:2365)
at 
org.apache.geode.internal.cache.GemFireCacheImpl.close(GemFireCacheImpl.java:1917)
at 
org.apache.geode.internal.cache.DiskStoreImpl.lambda$handleDiskAccessException$2(DiskStoreImpl.java:3380)
at java.lang.Thread.run(Thread.java:748)
{noformat}
{noformat}
java.lang.Throwable: KIRK InternalDistributedSystem closed 306674056
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1637)
at 
org.apache.geode.distributed.internal.InternalDistributedSystem.disconnect(InternalDistributedSystem.java:1225)
at 
org.apache.geode.internal.cache.

[jira] [Created] (GEODE-7994) Refactor Native Redis Acceptance Tests

2020-04-15 Thread Sarah Abbey (Jira)
Sarah Abbey created GEODE-7994:
--

 Summary: Refactor Native Redis Acceptance Tests
 Key: GEODE-7994
 URL: https://issues.apache.org/jira/browse/GEODE-7994
 Project: Geode
  Issue Type: Improvement
  Components: redis, tests
Reporter: Sarah Abbey


Rename Native Redis Acceptance tests and ensure all Jedis clients are closed in 
tearDown method.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7993) Gateway senders try to connect once at start up

2020-04-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7993:


Commit 88b3603babfb884e3dc7e3198f79cbbda720a822 in geode's branch 
refs/heads/develop from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=88b3603 ]

GEODE-7993: Document startup behavior of GW senders (#4965)



> Gateway senders try to connect once at start up
> ---
>
> Key: GEODE-7993
> URL: https://issues.apache.org/jira/browse/GEODE-7993
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Document that GW senders try once to connect to GW receivers upon GW sender 
> start up. If there's no receiver present at that time, it is not an error.  
> The GW sender tries again when it has a batch of events to send.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Resolved] (GEODE-7993) Gateway senders try to connect once at start up

2020-04-15 Thread Karen Smoler Miller (Jira)


 [ 
https://issues.apache.org/jira/browse/GEODE-7993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karen Smoler Miller resolved GEODE-7993.

Fix Version/s: 1.13.0
   Resolution: Fixed

> Gateway senders try to connect once at start up
> ---
>
> Key: GEODE-7993
> URL: https://issues.apache.org/jira/browse/GEODE-7993
> Project: Geode
>  Issue Type: Improvement
>  Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Fix For: 1.13.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Document that GW senders try once to connect to GW receivers upon GW sender 
> start up. If there's no receiver present at that time, it is not an error.  
> The GW sender tries again when it has a batch of events to send.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7985) roll benchmark baseline to 1.12 release

2020-04-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7985:


Commit c8d1048a63840919ea3389cf69be717e02a68a03 in geode's branch 
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c8d1048 ]

GEODE-7985: benchmark develop against 1.12.0 rather than 1.10.0 (#4957)

* GEODE-7985: benchmark develop against 1.12.0 rather than 1.10.0
* update release scripts to keep the baseline on develop in sync when a new 
minor is released

> roll benchmark baseline to 1.12 release
> ---
>
> Key: GEODE-7985
> URL: https://issues.apache.org/jira/browse/GEODE-7985
> Project: Geode
>  Issue Type: Bug
>  Components: benchmarks
>Reporter: Owen Nichols
>Assignee: Owen Nichols
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> current pipeline is still using 1.10.0 as baseline for benchmarks.  because 
> we've made some improvements since then, we won't be catching any regressions 
> against those gains



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7985) roll benchmark baseline to 1.12 release

2020-04-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7985:


Commit c8d1048a63840919ea3389cf69be717e02a68a03 in geode's branch 
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c8d1048 ]

GEODE-7985: benchmark develop against 1.12.0 rather than 1.10.0 (#4957)

* GEODE-7985: benchmark develop against 1.12.0 rather than 1.10.0
* update release scripts to keep the baseline on develop in sync when a new 
minor is released

> roll benchmark baseline to 1.12 release
> ---
>
> Key: GEODE-7985
> URL: https://issues.apache.org/jira/browse/GEODE-7985
> Project: Geode
>  Issue Type: Bug
>  Components: benchmarks
>Reporter: Owen Nichols
>Assignee: Owen Nichols
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> current pipeline is still using 1.10.0 as baseline for benchmarks.  because 
> we've made some improvements since then, we won't be catching any regressions 
> against those gains



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7985) roll benchmark baseline to 1.12 release

2020-04-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7985:


Commit c8d1048a63840919ea3389cf69be717e02a68a03 in geode's branch 
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c8d1048 ]

GEODE-7985: benchmark develop against 1.12.0 rather than 1.10.0 (#4957)

* GEODE-7985: benchmark develop against 1.12.0 rather than 1.10.0
* update release scripts to keep the baseline on develop in sync when a new 
minor is released

> roll benchmark baseline to 1.12 release
> ---
>
> Key: GEODE-7985
> URL: https://issues.apache.org/jira/browse/GEODE-7985
> Project: Geode
>  Issue Type: Bug
>  Components: benchmarks
>Reporter: Owen Nichols
>Assignee: Owen Nichols
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> current pipeline is still using 1.10.0 as baseline for benchmarks.  because 
> we've made some improvements since then, we won't be catching any regressions 
> against those gains



--
This message was sent by Atlassian Jira
(v8.3.4#803005)


[jira] [Commented] (GEODE-7985) roll benchmark baseline to 1.12 release

2020-04-15 Thread ASF subversion and git services (Jira)


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

ASF subversion and git services commented on GEODE-7985:


Commit c8d1048a63840919ea3389cf69be717e02a68a03 in geode's branch 
refs/heads/develop from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c8d1048 ]

GEODE-7985: benchmark develop against 1.12.0 rather than 1.10.0 (#4957)

* GEODE-7985: benchmark develop against 1.12.0 rather than 1.10.0
* update release scripts to keep the baseline on develop in sync when a new 
minor is released

> roll benchmark baseline to 1.12 release
> ---
>
> Key: GEODE-7985
> URL: https://issues.apache.org/jira/browse/GEODE-7985
> Project: Geode
>  Issue Type: Bug
>  Components: benchmarks
>Reporter: Owen Nichols
>Assignee: Owen Nichols
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> current pipeline is still using 1.10.0 as baseline for benchmarks.  because 
> we've made some improvements since then, we won't be catching any regressions 
> against those gains



--
This message was sent by Atlassian Jira
(v8.3.4#803005)