[jira] [Created] (GEODE-5427) Change pr-pipeline jobs to run on separately tagged workers
Sean Goller created GEODE-5427: -- Summary: Change pr-pipeline jobs to run on separately tagged workers Key: GEODE-5427 URL: https://issues.apache.org/jira/browse/GEODE-5427 Project: Geode Issue Type: Task Components: ci Reporter: Sean Goller In order to isolate resources used by the PR pipeline, ensure all jobs run on tagged workers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5426) Suites that do not modify behavior rerun tests in the pipeline
[
https://issues.apache.org/jira/browse/GEODE-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5426:
--
Labels: pull-request-available swat (was: swat)
> Suites that do not modify behavior rerun tests in the pipeline
> --
>
> Key: GEODE-5426
> URL: https://issues.apache.org/jira/browse/GEODE-5426
> Project: Geode
> Issue Type: Task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: pull-request-available, swat
>
> The only JUnit Suite that effects different behavior is
> {{CommandOverHttpDUnitTest}}. All others should be removed to steamline
> testing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5427) Change pr-pipeline jobs to run on separately tagged workers
[ https://issues.apache.org/jira/browse/GEODE-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5427: -- Labels: pull-request-available (was: ) > Change pr-pipeline jobs to run on separately tagged workers > --- > > Key: GEODE-5427 > URL: https://issues.apache.org/jira/browse/GEODE-5427 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > > In order to isolate resources used by the PR pipeline, ensure all jobs run on > tagged workers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5396) PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Hanson reassigned GEODE-5396:
--
Assignee: Mark Hanson (was: Jinmei Liao)
> PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
>
>
> Key: GEODE-5396
> URL: https://issues.apache.org/jira/browse/GEODE-5396
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Reporter: Dan Smith
>Assignee: Mark Hanson
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.tools.pulse.tests.ui.PulseAutomatedTest.html
>
>
> This test failed on 6a9a98b0bae561407230c5354fc95af0eae49268
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/131]
>
> {noformat}
> org.openqa.selenium.TimeoutException: timeout
> (Session info: headless chrome=67.0.3396.99)
> (Driver info: chromedriver=2.35.528139
> (47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-124-generic
> x86_64) (WARNING: The server did not provide any stacktrace information)
> Command duration or timeout: 0 milliseconds
> Build info: version: '3.9.1', revision: '63f7b50', time:
> '2018-02-07T22:25:02.294Z'
> System info: host: '3d781bee-3034-433d-6295-dafc92f1c71a', ip: '10.254.0.50',
> os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-124-generic',
> java.version: '1.8.0_171'
> Driver info: org.openqa.selenium.chrome.ChromeDriver
> Capabilities {acceptInsecureCerts: false, acceptSslCerts: false,
> applicationCacheEnabled: false, browserConnectionEnabled: false, browserName:
> chrome, chrome: {chromedriverVersion: 2.35.528139 (47ead77cb35ad2...,
> userDataDir: /tmp/build/ae3c03f4/built-g...}, cssSelectorsEnabled: true,
> databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false,
> javascriptEnabled: true, locationContextEnabled: true,
> mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled:
> false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX,
> rotatable: false, setWindowRect: true, takesHeapSnapshot: true,
> takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: ,
> version: 67.0.3396.99, webStorageEnabled: true}
> Session ID: 352271503dab2578e934f08be4bfdd50
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
> at
> org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
> at
> org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
> at
> org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
> at
> org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
> at
> org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:160)
> at
> org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
> at
> org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601)
> at
> org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:325)
> at
> org.apache.geode.tools.pulse.tests.rules.WebDriverRule.before(WebDriverRule.java:61)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
> 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
>
[jira] [Updated] (GEODE-5424) Change all awaitility use to a standard timeout
[ https://issues.apache.org/jira/browse/GEODE-5424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5424: - Labels: swat (was: ) > Change all awaitility use to a standard timeout > --- > > Key: GEODE-5424 > URL: https://issues.apache.org/jira/browse/GEODE-5424 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Priority: Major > Labels: swat > > Lets change all use of Awaitility in geode to use a standard timeout of 5 > minutes. > We could do this by introducing a new static factory that wraps > Awaitility.await(), eg GeodeAwaitility.await() that sets the timeout to be 5 > minutes, and bulk change all of our use of Awaitility to GeodeAwaitility. > While we're at it, we might also want to change the default poll delay and > poll interval to something smaller if that will speed up our tests. > Relevant discussion thread on geode dev list: > https://geode.markmail.org/thread/cm2cngqupjsbipch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5424) Change all awaitility use to a standard timeout
Dan Smith created GEODE-5424: Summary: Change all awaitility use to a standard timeout Key: GEODE-5424 URL: https://issues.apache.org/jira/browse/GEODE-5424 Project: Geode Issue Type: Task Components: tests Reporter: Dan Smith Lets change all use of Awaitility in geode to use a standard timeout of 5 minutes. We could do this by introducing a new static factory that wraps Awaitility.await(), eg GeodeAwaitility.await() that sets the timeout to be 5 minutes, and bulk change all of our use of Awaitility to GeodeAwaitility. While we're at it, we might also want to change the default poll delay and poll interval to something smaller if that will speed up our tests. Relevant discussion thread on geode dev list: https://geode.markmail.org/thread/cm2cngqupjsbipch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5299) Correct failure resulting from potential race condition in geode-wan:CreateRegionCommandDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542123#comment-16542123
]
ASF subversion and git services commented on GEODE-5299:
Commit 84e911cb22097319aa1130fdd02a57d0354c9cc4 in geode's branch
refs/heads/develop from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=84e911c ]
GEODE-5295: Improve member WaitUntilX methods (#2039)
* Improve error reporting in the event of a WaitUntil timeout.
* Renamed methods to avoid future developer error similar to GEODE-5299
> Correct failure resulting from potential race condition in
> geode-wan:CreateRegionCommandDUnitTest
> -
>
> Key: GEODE-5299
> URL: https://issues.apache.org/jira/browse/GEODE-5299
> Project: Geode
> Issue Type: Test
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> A recent commit contains the line the effective sequence:
> {noformat}
> locator = lsRule.startLocatorVM(0);
> server1 = lsRule.startServerVM(1, locator.getPort());
> server2 = lsRule.startServerVM(2, locator.getPort());
> gfsh.connectAndVerify(locator);String regionName =
> testName.getMethodName();
> String gatewaySenderName = "gatewaySender";
> IgnoredException.addIgnoredException("could not get remote locator
> information");
> gfsh.executeAndAssertThat(
> "create gateway-sender --parallel=true
> --remote-distributed-system-id=2 --id="
> + gatewaySenderName)
> .statusIsSuccess();
> locator.waitTilGatewaySendersAreReady(1);
> {noformat}
> Notably, the {{waitTilGatewaySendersAreReady}} expects to find 1 gateway
> mbean from the two servers on which the gateway will be created.
> However, the underlying implementation of the method expects to find
> *exactly* 1 bean, meaning that if the gateway creation and bean registration
> occurs before the {{wait*}} method is called, the test will fail to a hang
> despite correct execution.
> The true root cause of this error is likely the ambiguity in the method and
> variable naming. Consider renaming this method and related to be explicitly
> clear to future developers that these methods have exact expectation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5295) Improve error reporting in ClusterStartupRule await methods
[ https://issues.apache.org/jira/browse/GEODE-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542122#comment-16542122 ] ASF subversion and git services commented on GEODE-5295: Commit 84e911cb22097319aa1130fdd02a57d0354c9cc4 in geode's branch refs/heads/develop from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=84e911c ] GEODE-5295: Improve member WaitUntilX methods (#2039) * Improve error reporting in the event of a WaitUntil timeout. * Renamed methods to avoid future developer error similar to GEODE-5299 > Improve error reporting in ClusterStartupRule await methods > --- > > Key: GEODE-5295 > URL: https://issues.apache.org/jira/browse/GEODE-5295 > Project: Geode > Issue Type: Improvement >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > The family of methods that wait until the cluster's gateways / regions / disk > stores are ready will occasionally hang, having a number not equal to the > expected number of beans. In these cases, it unclear if the number of > expected element beans is too few (indicating a delay or failure to start) or > too many (indicating a failure to destroy a previous test). > Failure reporting should be improved to indicate the nature of failure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5426) Suites that do not modify behavior rerun tests in the pipeline
[
https://issues.apache.org/jira/browse/GEODE-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg reassigned GEODE-5426:
---
Assignee: Patrick Rhomberg
> Suites that do not modify behavior rerun tests in the pipeline
> --
>
> Key: GEODE-5426
> URL: https://issues.apache.org/jira/browse/GEODE-5426
> Project: Geode
> Issue Type: Task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: swat
>
> The only JUnit Suite that effects different behavior is
> {{CommandOverHttpDUnitTest}}. All others should be removed to steamline
> testing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5426) Suites that do not modify behavior rerun tests in the pipeline
[
https://issues.apache.org/jira/browse/GEODE-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg updated GEODE-5426:
Labels: swat (was: )
> Suites that do not modify behavior rerun tests in the pipeline
> --
>
> Key: GEODE-5426
> URL: https://issues.apache.org/jira/browse/GEODE-5426
> Project: Geode
> Issue Type: Task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: swat
>
> The only JUnit Suite that effects different behavior is
> {{CommandOverHttpDUnitTest}}. All others should be removed to steamline
> testing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5426) Suites that do not modify behavior rerun tests in the pipeline
Patrick Rhomberg created GEODE-5426:
---
Summary: Suites that do not modify behavior rerun tests in the
pipeline
Key: GEODE-5426
URL: https://issues.apache.org/jira/browse/GEODE-5426
Project: Geode
Issue Type: Task
Reporter: Patrick Rhomberg
The only JUnit Suite that effects different behavior is
{{CommandOverHttpDUnitTest}}. All others should be removed to steamline
testing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5423) Improve Gradle configuration performance
[ https://issues.apache.org/jira/browse/GEODE-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5423: -- Labels: pull-request-available (was: ) > Improve Gradle configuration performance > > > Key: GEODE-5423 > URL: https://issues.apache.org/jira/browse/GEODE-5423 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Robert Houghton >Priority: Major > Labels: pull-request-available > > Clean builds spend minutes of time doing download and unzip of old Geode > builds during `configure` step of Gradle. Moving this to the `execute` step > allows other tasks to run in parallel, and allows caching of the dependency, > instead of checking its existence on every build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5377) LuceneQueriesReindexDUnitTest recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK) hangs DUnit pipeline
[
https://issues.apache.org/jira/browse/GEODE-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542213#comment-16542213
]
ASF subversion and git services commented on GEODE-5377:
Commit 159018292d59486df53b61b0e438d3e69fffd6f4 in geode's branch
refs/heads/develop from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1590182 ]
GEODE-5377: wait till threads to finish before exiting the test (#2106)
Co-authored-by: Finn Southerland
* put more comments and make join call wait on explicit timeout period
* assert before creating index on the other datastore
> LuceneQueriesReindexDUnitTest
> recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK) hangs
> DUnit pipeline
> -
>
> Key: GEODE-5377
> URL: https://issues.apache.org/jira/browse/GEODE-5377
> Project: Geode
> Issue Type: Sub-task
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/71]
>
> Thread dump analyzer shows these two threads are blocked:
> h3. RMI TCP Connection(9)-172.17.0.4
> RMI TCP Connection(9)-172.17.0.4
> Stack Trace is:
>
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySender.waitForRunningStatus(AbstractGatewaySender.java:738)
> - locked {color:#FF}<0xe0b9cba8>{color} (a java.lang.Object)
> at
> org.apache.geode.cache.asyncqueue.internal.ParallelAsyncEventQueueImpl.start(ParallelAsyncEventQueueImpl.java:83)
> at
> org.apache.geode.cache.asyncqueue.internal.AsyncEventQueueFactoryImpl.create(AsyncEventQueueFactoryImpl.java:162)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexImpl.createAEQ(LuceneIndexImpl.java:177)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexImpl.createAEQ(LuceneIndexImpl.java:171)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.beforeDataRegionCreated(LuceneServiceImpl.java:369)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndexOnExistingRegion(LuceneServiceImpl.java:265)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:221)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:188)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexFactoryImpl.create(LuceneIndexFactoryImpl.java:70)
> at
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest.lambda$recreateIndexWithDifferentFieldsShouldFail$88e94ee2$1(LuceneQueriesReindexDUnitTest.java:156)
> at
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest$$Lambda$105/1606286154.run(Unknown
> Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> at
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:835)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$7/957256838.run(Unknown
> Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Locked ownable synchronizers:
> -
[jira] [Resolved] (GEODE-5377) LuceneQueriesReindexDUnitTest recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK) hangs DUnit pipeline
[
https://issues.apache.org/jira/browse/GEODE-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao resolved GEODE-5377.
Resolution: Fixed
> LuceneQueriesReindexDUnitTest
> recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK) hangs
> DUnit pipeline
> -
>
> Key: GEODE-5377
> URL: https://issues.apache.org/jira/browse/GEODE-5377
> Project: Geode
> Issue Type: Sub-task
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/71]
>
> Thread dump analyzer shows these two threads are blocked:
> h3. RMI TCP Connection(9)-172.17.0.4
> RMI TCP Connection(9)-172.17.0.4
> Stack Trace is:
>
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySender.waitForRunningStatus(AbstractGatewaySender.java:738)
> - locked {color:#FF}<0xe0b9cba8>{color} (a java.lang.Object)
> at
> org.apache.geode.cache.asyncqueue.internal.ParallelAsyncEventQueueImpl.start(ParallelAsyncEventQueueImpl.java:83)
> at
> org.apache.geode.cache.asyncqueue.internal.AsyncEventQueueFactoryImpl.create(AsyncEventQueueFactoryImpl.java:162)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexImpl.createAEQ(LuceneIndexImpl.java:177)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexImpl.createAEQ(LuceneIndexImpl.java:171)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.beforeDataRegionCreated(LuceneServiceImpl.java:369)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndexOnExistingRegion(LuceneServiceImpl.java:265)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:221)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:188)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexFactoryImpl.create(LuceneIndexFactoryImpl.java:70)
> at
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest.lambda$recreateIndexWithDifferentFieldsShouldFail$88e94ee2$1(LuceneQueriesReindexDUnitTest.java:156)
> at
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest$$Lambda$105/1606286154.run(Unknown
> Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> at
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:835)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$7/957256838.run(Unknown
> Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Locked ownable synchronizers:
> - {color:#FF}<0xe09a0078>{color} (a
> java.util.concurrent.ThreadPoolExecutor$Worker)
> - {color:#FF}<0xe0b8ad88>{color} (a
> java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
>
>
> h3. RMI TCP Connection(14)-172.17.0.4
> RMI TCP Connection(14)-172.17.0.4
> Stack Trace is:
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for {color:#FF}<0xe0b8ad88>{color} (a
>
[jira] [Resolved] (GEODE-5370) DistributedTest task on CI occasionally exceeds timeout
[ https://issues.apache.org/jira/browse/GEODE-5370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao resolved GEODE-5370. Resolution: Fixed > DistributedTest task on CI occasionally exceeds timeout > --- > > Key: GEODE-5370 > URL: https://issues.apache.org/jira/browse/GEODE-5370 > Project: Geode > Issue Type: Bug >Reporter: Alexander Murmann >Assignee: Jinmei Liao >Priority: Major > Labels: ci, concourse, flaky, swat > > Occasionally the CI job fails because it exceeds the 8 hour timeout. The job > usually takes ~3 hours, so this is definitely outside the expected variation. > See the following runs: > [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/88] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/79] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/77] > [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/71] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5396) PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-5396:
--
Labels: pull-request-available swat (was: swat)
> PulseAutomatedTest.clickRZGridMembersNavigationTest failed in CI
>
>
> Key: GEODE-5396
> URL: https://issues.apache.org/jira/browse/GEODE-5396
> Project: Geode
> Issue Type: Bug
> Components: pulse
>Reporter: Dan Smith
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available, swat
> Attachments: Test results - Class
> org.apache.geode.tools.pulse.tests.ui.PulseAutomatedTest.html
>
>
> This test failed on 6a9a98b0bae561407230c5354fc95af0eae49268
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/UITests/builds/131]
>
> {noformat}
> org.openqa.selenium.TimeoutException: timeout
> (Session info: headless chrome=67.0.3396.99)
> (Driver info: chromedriver=2.35.528139
> (47ead77cb35ad2a9a83248b292151462a66cd881),platform=Linux 4.4.0-124-generic
> x86_64) (WARNING: The server did not provide any stacktrace information)
> Command duration or timeout: 0 milliseconds
> Build info: version: '3.9.1', revision: '63f7b50', time:
> '2018-02-07T22:25:02.294Z'
> System info: host: '3d781bee-3034-433d-6295-dafc92f1c71a', ip: '10.254.0.50',
> os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-124-generic',
> java.version: '1.8.0_171'
> Driver info: org.openqa.selenium.chrome.ChromeDriver
> Capabilities {acceptInsecureCerts: false, acceptSslCerts: false,
> applicationCacheEnabled: false, browserConnectionEnabled: false, browserName:
> chrome, chrome: {chromedriverVersion: 2.35.528139 (47ead77cb35ad2...,
> userDataDir: /tmp/build/ae3c03f4/built-g...}, cssSelectorsEnabled: true,
> databaseEnabled: false, handlesAlerts: true, hasTouchScreen: false,
> javascriptEnabled: true, locationContextEnabled: true,
> mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled:
> false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX,
> rotatable: false, setWindowRect: true, takesHeapSnapshot: true,
> takesScreenshot: true, unexpectedAlertBehaviour: , unhandledPromptBehavior: ,
> version: 67.0.3396.99, webStorageEnabled: true}
> Session ID: 352271503dab2578e934f08be4bfdd50
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
> at
> org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
> at
> org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
> at
> org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80)
> at
> org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44)
> at
> org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:160)
> at
> org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
> at
> org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601)
> at
> org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:325)
> at
> org.apache.geode.tools.pulse.tests.rules.WebDriverRule.before(WebDriverRule.java:61)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
> 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
>
[jira] [Assigned] (GEODE-5425) Improve quality of concourse_job_performance.py
[
https://issues.apache.org/jira/browse/GEODE-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg reassigned GEODE-5425:
---
Assignee: Patrick Rhomberg
> Improve quality of concourse_job_performance.py
> ---
>
> Key: GEODE-5425
> URL: https://issues.apache.org/jira/browse/GEODE-5425
> Project: Geode
> Issue Type: Task
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
> Labels: swat
>
> This script could use general cleanup to adhere more closely to PEP-8.
> Additionally:
> * Team target should be parameterized
> * The fetch limit for the initial build summary should be included in the GET
> if more than 100 builds are to be (initially) examined
> * Perhaps optionally, reporting should be able to group by test class, method
> name (for those extending TestBase classes)
> * Optionally, highlight / exclude those failures that resulted from a
> {{timeout exceeded}} failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5425) Improve quality of concourse_job_performance.py
Patrick Rhomberg created GEODE-5425:
---
Summary: Improve quality of concourse_job_performance.py
Key: GEODE-5425
URL: https://issues.apache.org/jira/browse/GEODE-5425
Project: Geode
Issue Type: Task
Reporter: Patrick Rhomberg
This script could use general cleanup to adhere more closely to PEP-8.
Additionally:
* Team target should be parameterized
* The fetch limit for the initial build summary should be included in the GET
if more than 100 builds are to be (initially) examined
* Perhaps optionally, reporting should be able to group by test class, method
name (for those extending TestBase classes)
* Optionally, highlight / exclude those failures that resulted from a {{timeout
exceeded}} failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5425) Improve quality of concourse_job_performance.py
[
https://issues.apache.org/jira/browse/GEODE-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Rhomberg updated GEODE-5425:
Labels: swat (was: )
> Improve quality of concourse_job_performance.py
> ---
>
> Key: GEODE-5425
> URL: https://issues.apache.org/jira/browse/GEODE-5425
> Project: Geode
> Issue Type: Task
>Reporter: Patrick Rhomberg
>Priority: Major
> Labels: swat
>
> This script could use general cleanup to adhere more closely to PEP-8.
> Additionally:
> * Team target should be parameterized
> * The fetch limit for the initial build summary should be included in the GET
> if more than 100 builds are to be (initially) examined
> * Perhaps optionally, reporting should be able to group by test class, method
> name (for those extending TestBase classes)
> * Optionally, highlight / exclude those failures that resulted from a
> {{timeout exceeded}} failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-1703) SUPERFLAKY: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails assertion: Region not created within30000
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1703:
-
Summary: SUPERFLAKY:
PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
assertion: Region not created within3 (was: CI failure:
PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
assertion: Region not created within3)
> SUPERFLAKY:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId fails
> assertion: Region not created within3
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: regions, tests
>Reporter: Kirk Lund
>Priority: Minor
> Labels: CI, flaky, swat
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-577) SUPERFLAKY: QueryMonitorDUnitTest is flaky and needs to be rewritten (60 failures in 200)
[
https://issues.apache.org/jira/browse/GEODE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-577:
Summary: SUPERFLAKY: QueryMonitorDUnitTest is flaky and needs to be
rewritten (60 failures in 200) (was: QueryMonitorDUnitTest is flaky and needs
to be rewritten (60 failures in 200))
> SUPERFLAKY: QueryMonitorDUnitTest is flaky and needs to be rewritten (60
> failures in 200)
> -
>
> Key: GEODE-577
> URL: https://issues.apache.org/jira/browse/GEODE-577
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Priority: Major
> Labels: CI, Flaky, swat
> Fix For: 1.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> GemFire_develop_DistributedTests
> Private Build #38 (Nov 15, 2015 3:12:12 PM)
> Revision: b7f640cf2e41acb40a531cc7abbee932a9ea093c
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> Error Message
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1
> running on Host latvia.gemstone.com with 4 VMs
> {noformat}
> Stacktrace
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest$14.run in VM 1
> running on Host latvia.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:369)
> at dunit.VM.invoke(VM.java:312)
> at dunit.VM.invoke(VM.java:266)
> at
> com.gemstone.gemfire.cache.query.dunit.QueryMonitorDUnitTest.testQueryExecutionLocally(QueryMonitorDUnitTest.java:493)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at sun.reflect.GeneratedMethodAccessor123.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
>
[jira] [Commented] (GEODE-5429) SUPERFLAKY: Multiple failures from RestAPIsWithSSLDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542308#comment-16542308
]
Dan Smith commented on GEODE-5429:
--
Below are links to the failures. Request access to the staging pipeline to view
these links.
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithMultipleCipherSuite:
2 failures (99.11894273127754% success rate)
Failed build 60 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/60
Failed build 59 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/59
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSimpleSSLWithMultiKey_KeyStore_WithInvalidClientKey:
13 failures (94.27312775330397% success rate)
Failed build 210 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/210
Failed build 193 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/193
Failed build 97 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/97
Failed build 94 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/94
Failed build 79 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/79
Failed build 75 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/75
Failed build 70 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/70
Failed build 60 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/60
Failed build 59 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/59
Failed build 56 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/56
Failed build 55 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/55
Failed build 53 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/53
Failed build 52 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/52
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithoutKeyStoreTypeLegacy:
3 failures (98.6784140969163% success rate)
Failed build 210 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/210
Failed build 193 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/193
Failed build 79 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/79
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithTLSv11Protocol:
2 failures (99.11894273127754% success rate)
Failed build 97 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/97
Failed build 60 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/60
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testWithMultipleProtocolLegacy:
1 failures (99.55947136563876% success rate)
Failed build 83 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/83
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithTLSv12ProtocolLegacy:
7 failures (96.91629955947137% success rate)
Failed build 83 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/83
Failed build 70 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/70
Failed build 60 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/60
Failed build 56 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/56
Failed build 55 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/55
Failed build 53 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/53
Failed build 52 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/52
Many of these (all?) seem to be a force disconnect. Maybe these tests are
confguring too low of a member timeout or stressing the system in some way?
{noformat}
[jira] [Updated] (GEODE-3530) All DistributedTests that extend CliCommandTestBase are Flaky
[ https://issues.apache.org/jira/browse/GEODE-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-3530: --- Description: All DistributedTests that extend CliCommandTestBase are Flaky. The tests need to be rewritten with GfshShellConnectionRule so we can delete CliCommandTestBase. List of test classes extending CliCommandTestBase and existing Flaky tickets: * -AlterRegionCommandDUnitTest- (GEODE-3018) * -ClusterConfigurationDUnitTest- (GEODE-1333, GEODE-1334) * -ConfigCommandsDUnitTest- (GEODE-1449) * -ConnectCommandWithHttpAndSSLDUnitTest- * -CreateAlterDestroyRegionCommandsDUnitTest- (GEODE-973, GEODE-2009, GEODE-3018) * -CreateRegionCommandDUnitTest- (GEODE-973) * -DescribeClientCommandDUnitTest- (GEODE-910) * -DestroyRegionCommandDUnitTest- * -DiskStoreCommandsDUnitTest- (GEODE-1206, GEODE-1406, GEODE-2102) * -DurableClientCommandsDUnitTest- (GEODE-1705, GEODE-3404, GEODE-3359) * -FunctionCommandsDUnitTest- (GEODE-1563) * -GemfireDataCommandsDUnitTest- (GEODE-1182, GEODE-1249, GEODE-1404, GEODE-1430, GEODE-1487, GEODE-1496, GEODE-1561, GEODE-1822, GEODE-2006) * -GetCommandOnRegionWithCacheLoaderDuringCacheMissDUnitTest- (Does not exist) * LauncherLifecycleCommandsDUnitTest * -ListAndDescribeDiskStoreCommandsDUnitTest (does not exist)- * ListClientCommandDUnitTest (GEODE-908) (Jinmei/Finn) * -ListIndexCommandDUnitTest- * -LuceneIndexCommandsDUnitTest- (does not exist) * -MiscellaneousCommandsDUnitTest (GEODE-1034, GEODE-1385, GEODE-1518, GEODE-1605, GEODE-1706, GEODE-2126)- * -QueueCommandsDUnitTest- (does not exist) (GEODE-1429, GEODE-1976) * RebalanceCommandDistributedTest (Finn) * RebalanceCommandOverHttpDistributedTest (Finn) * ShellCommandsDUnitTest (GEODE-989) * -ShowMetricsDUnitTest- (GEODE-1764) * -ShowStackTraceDUnitTest- (does not exist) * -WANCommandTestBase- (and subclasses) * ClientCommandsTestUtils * ShellCommandsDUnitTest (Jinmei) Test classes that *use* but do not extend CliCommandTestBase: * CommandOverrHttpDUnitTest was: All DistributedTests that extend CliCommandTestBase are Flaky. The tests need to be rewritten with GfshShellConnectionRule so we can delete CliCommandTestBase. List of test classes extending CliCommandTestBase and existing Flaky tickets: * -AlterRegionCommandDUnitTest- (GEODE-3018) * -ClusterConfigurationDUnitTest- (GEODE-1333, GEODE-1334) * -ConfigCommandsDUnitTest- (GEODE-1449) * -ConnectCommandWithHttpAndSSLDUnitTest- * -CreateAlterDestroyRegionCommandsDUnitTest- (GEODE-973, GEODE-2009, GEODE-3018) * -CreateRegionCommandDUnitTest- (GEODE-973) * -DescribeClientCommandDUnitTest- (GEODE-910) * -DestroyRegionCommandDUnitTest- * -DiskStoreCommandsDUnitTest- (GEODE-1206, GEODE-1406, GEODE-2102) * -DurableClientCommandsDUnitTest- (GEODE-1705, GEODE-3404, GEODE-3359) * -FunctionCommandsDUnitTest- (GEODE-1563) * -GemfireDataCommandsDUnitTest- (GEODE-1182, GEODE-1249, GEODE-1404, GEODE-1430, GEODE-1487, GEODE-1496, GEODE-1561, GEODE-1822, GEODE-2006) * -GetCommandOnRegionWithCacheLoaderDuringCacheMissDUnitTest- (Does not exist) * LauncherLifecycleCommandsDUnitTest * -ListAndDescribeDiskStoreCommandsDUnitTest (does not exist)- * ListClientCommandDUnitTest (GEODE-908) (Jinmei/Finn) * -ListIndexCommandDUnitTest- * -LuceneIndexCommandsDUnitTest- (does not exist) * -MiscellaneousCommandsDUnitTest (GEODE-1034, GEODE-1385, GEODE-1518, GEODE-1605, GEODE-1706, GEODE-2126)- * -QueueCommandsDUnitTest- (does not exist) (GEODE-1429, GEODE-1976) * RebalanceCommandDistributedTest (Finn) * RebalanceCommandOverHttpDistributedTest (Finn) * ShellCommandsDUnitTest (GEODE-989) * -ShowMetricsDUnitTest- (GEODE-1764) * -ShowStackTraceDUnitTest- (does not exist) * -WANCommandTestBase- (and subclasses) * ClientCommandsTestUtils Test classes that *use* but do not extend CliCommandTestBase: * CommandOverrHttpDUnitTest > All DistributedTests that extend CliCommandTestBase are Flaky > - > > Key: GEODE-3530 > URL: https://issues.apache.org/jira/browse/GEODE-3530 > Project: Geode > Issue Type: Bug > Components: management, tests >Reporter: Kirk Lund >Assignee: Jinmei Liao >Priority: Major > Labels: CliCommandTestBase, DistributedTest, Flaky, > pull-request-available, swat > Time Spent: 2h > Remaining Estimate: 0h > > All DistributedTests that extend CliCommandTestBase are Flaky. The tests need > to be rewritten with GfshShellConnectionRule so we can delete > CliCommandTestBase. > List of test classes extending CliCommandTestBase and existing Flaky tickets: > * -AlterRegionCommandDUnitTest- (GEODE-3018) > * -ClusterConfigurationDUnitTest- (GEODE-1333, GEODE-1334) > * -ConfigCommandsDUnitTest- (GEODE-1449) > * -ConnectCommandWithHttpAndSSLDUnitTest- > *
[jira] [Commented] (GEODE-5404) Optimize performance of client/server distinct order-by queries with integrated security
[
https://issues.apache.org/jira/browse/GEODE-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542297#comment-16542297
]
ASF subversion and git services commented on GEODE-5404:
Commit a96edf2e6fc988bd96ce78e6011d080494ec18df in geode's branch
refs/heads/feature/GEODE-5145 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a96edf2 ]
GEODE-5404: Created static default whitelist and modified to call length
> Optimize performance of client/server distinct order-by queries with
> integrated security
>
>
> Key: GEODE-5404
> URL: https://issues.apache.org/jira/browse/GEODE-5404
> Project: Geode
> Issue Type: Bug
> Components: querying
>Reporter: Barry Oglesby
>Assignee: Barry Oglesby
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The performance of distinct order-by queries along with integrated security
> has degraded.
> With the query below and integrated security, \{{SelectResults.size}}
> repeatedly causes the whitelist to be created while re-ordering the results.
> \{{SelectResults.size}} is called every time through the loop in
> \{{BaseCommandQuery.sendResultsAsObjectArray}}.
> {noformat}
> select distinct * from /data where cusip = $1 order by id asc limit 500
> {noformat}
> In current:
> {noformat}
> Query ' select distinct * from /data where cusip = 'AAPL' order by id
> asc limit 500' returned 500 entries in 175979 ms
> Query ' select distinct * from /data where cusip = 'AAPL' order by id
> asc limit 500' returned 500 entries in 173280 ms
> {noformat}
> In Geode 1.2.0:
> {noformat}
> Query ' select distinct * from /data where cusip = 'AAPL' order by id
> asc limit 500' returned 500 entries in 7270 ms
> Query ' select distinct * from /data where cusip = 'AAPL' order by id
> asc limit 500' returned 500 entries in 7303 ms
> {noformat}
> Here is a stack trace showing ths issue:
> {noformat}
> "ServerConnection on port 59856 Thread 1" #83 prio=5 os_prio=31
> tid=0x7fe66191f000 nid=0xbf07 runnable [0x7ea9a000]
> java.lang.Thread.State: RUNNABLE
> at java.util.HashMap.putVal(HashMap.java:628)
> at java.util.HashMap.put(HashMap.java:611)
> at java.util.HashSet.add(HashSet.java:219)
> at
> org.apache.geode.cache.query.internal.RestrictedMethodInvocationAuthorizer.createWhiteList(RestrictedMethodInvocationAuthorizer.java:48)
> at
> org.apache.geode.cache.query.internal.RestrictedMethodInvocationAuthorizer.(RestrictedMethodInvocationAuthorizer.java:42)
> at
> org.apache.geode.cache.query.internal.DefaultQueryService.(DefaultQueryService.java:126)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl.getQueryService(GemFireCacheImpl.java:4199)
> at
> org.apache.geode.cache.query.internal.PathUtils.evaluateAttribute(PathUtils.java:76)
> at
> org.apache.geode.cache.query.internal.CompiledPath.evaluate(CompiledPath.java:147)
> at
> org.apache.geode.cache.query.internal.CompiledSortCriterion.evaluate(CompiledSortCriterion.java:72)
> at
> org.apache.geode.cache.query.internal.OrderByComparator.evaluateSortCriteria(OrderByComparator.java:78)
> at
> org.apache.geode.cache.query.internal.OrderByComparator.compare(OrderByComparator.java:111)
> at
> org.apache.geode.cache.query.internal.NWayMergeResults$NWayMergeResultsCollection$NWayMergeIterator.compare(NWayMergeResults.java:310)
> at
> org.apache.geode.cache.query.internal.NWayMergeResults$NWayMergeResultsCollection$NWayMergeDistinctIterator.hasNext(NWayMergeResults.java:396)
> at
> org.apache.geode.cache.query.internal.utils.LimitIterator.hasNext(LimitIterator.java:39)
> at
> org.apache.geode.cache.query.internal.NWayMergeResults$NWayMergeResultsCollection$NWayMergeIterator$IteratorWrapper.move(NWayMergeResults.java:346)
> at
> org.apache.geode.cache.query.internal.NWayMergeResults$NWayMergeResultsCollection$NWayMergeDistinctIterator.hasNext(NWayMergeResults.java:380)
> at
> org.apache.geode.cache.query.internal.utils.LimitIterator.hasNext(LimitIterator.java:39)
> at
> org.apache.geode.cache.query.internal.NWayMergeResults$NWayMergeResultsCollection.size(NWayMergeResults.java:193)
> at
> org.apache.geode.cache.query.internal.NWayMergeResults.size(NWayMergeResults.java:68)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.sendResultsAsObjectArray(BaseCommandQuery.java:367)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.processQueryUsingParams(BaseCommandQuery.java:218)
> at
> org.apache.geode.internal.cache.tier.sockets.BaseCommandQuery.processQuery(BaseCommandQuery.java:60)
> at
>
[jira] [Commented] (GEODE-5145) Lucene index needs to support being destroyed while region is being created
[ https://issues.apache.org/jira/browse/GEODE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542305#comment-16542305 ] ASF subversion and git services commented on GEODE-5145: Commit ce67725770664bebefd34c23b998344d4a0a334f in geode's branch refs/heads/feature/GEODE-5145 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ce67725 ] GEODE-5145: Incorporated review comments > Lucene index needs to support being destroyed while region is being created > --- > > Key: GEODE-5145 > URL: https://issues.apache.org/jira/browse/GEODE-5145 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Barry Oglesby >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > Attempting to destroy a lucene index while the region is being created may > leave the lucene service in an inconsistent state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5377) LuceneQueriesReindexDUnitTest recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK) hangs DUnit pipeline
[
https://issues.apache.org/jira/browse/GEODE-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542302#comment-16542302
]
ASF subversion and git services commented on GEODE-5377:
Commit 159018292d59486df53b61b0e438d3e69fffd6f4 in geode's branch
refs/heads/feature/GEODE-5145 from jinmeiliao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1590182 ]
GEODE-5377: wait till threads to finish before exiting the test (#2106)
Co-authored-by: Finn Southerland
* put more comments and make join call wait on explicit timeout period
* assert before creating index on the other datastore
> LuceneQueriesReindexDUnitTest
> recreateIndexWithDifferentFieldsShouldFail(PARTITION_OVERFLOW_TO_DISK) hangs
> DUnit pipeline
> -
>
> Key: GEODE-5377
> URL: https://issues.apache.org/jira/browse/GEODE-5377
> Project: Geode
> Issue Type: Sub-task
>Reporter: Jinmei Liao
>Assignee: Jinmei Liao
>Priority: Major
> Labels: pull-request-available, swat
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/71]
>
> Thread dump analyzer shows these two threads are blocked:
> h3. RMI TCP Connection(9)-172.17.0.4
> RMI TCP Connection(9)-172.17.0.4
> Stack Trace is:
>
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at
> org.apache.geode.internal.cache.wan.AbstractGatewaySender.waitForRunningStatus(AbstractGatewaySender.java:738)
> - locked {color:#FF}<0xe0b9cba8>{color} (a java.lang.Object)
> at
> org.apache.geode.cache.asyncqueue.internal.ParallelAsyncEventQueueImpl.start(ParallelAsyncEventQueueImpl.java:83)
> at
> org.apache.geode.cache.asyncqueue.internal.AsyncEventQueueFactoryImpl.create(AsyncEventQueueFactoryImpl.java:162)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexImpl.createAEQ(LuceneIndexImpl.java:177)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexImpl.createAEQ(LuceneIndexImpl.java:171)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.beforeDataRegionCreated(LuceneServiceImpl.java:369)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndexOnExistingRegion(LuceneServiceImpl.java:265)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:221)
> at
> org.apache.geode.cache.lucene.internal.LuceneServiceImpl.createIndex(LuceneServiceImpl.java:188)
> at
> org.apache.geode.cache.lucene.internal.LuceneIndexFactoryImpl.create(LuceneIndexFactoryImpl.java:70)
> at
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest.lambda$recreateIndexWithDifferentFieldsShouldFail$88e94ee2$1(LuceneQueriesReindexDUnitTest.java:156)
> at
> org.apache.geode.cache.lucene.LuceneQueriesReindexDUnitTest$$Lambda$105/1606286154.run(Unknown
> Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hydra.MethExecutor.executeObject(MethExecutor.java:244)
> at
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:835)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler$$Lambda$7/957256838.run(Unknown
> Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Locked ownable synchronizers:
> -
[jira] [Commented] (GEODE-5299) Correct failure resulting from potential race condition in geode-wan:CreateRegionCommandDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542300#comment-16542300
]
ASF subversion and git services commented on GEODE-5299:
Commit 84e911cb22097319aa1130fdd02a57d0354c9cc4 in geode's branch
refs/heads/feature/GEODE-5145 from [~prhomberg]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=84e911c ]
GEODE-5295: Improve member WaitUntilX methods (#2039)
* Improve error reporting in the event of a WaitUntil timeout.
* Renamed methods to avoid future developer error similar to GEODE-5299
> Correct failure resulting from potential race condition in
> geode-wan:CreateRegionCommandDUnitTest
> -
>
> Key: GEODE-5299
> URL: https://issues.apache.org/jira/browse/GEODE-5299
> Project: Geode
> Issue Type: Test
>Reporter: Patrick Rhomberg
>Assignee: Patrick Rhomberg
>Priority: Major
>
> A recent commit contains the line the effective sequence:
> {noformat}
> locator = lsRule.startLocatorVM(0);
> server1 = lsRule.startServerVM(1, locator.getPort());
> server2 = lsRule.startServerVM(2, locator.getPort());
> gfsh.connectAndVerify(locator);String regionName =
> testName.getMethodName();
> String gatewaySenderName = "gatewaySender";
> IgnoredException.addIgnoredException("could not get remote locator
> information");
> gfsh.executeAndAssertThat(
> "create gateway-sender --parallel=true
> --remote-distributed-system-id=2 --id="
> + gatewaySenderName)
> .statusIsSuccess();
> locator.waitTilGatewaySendersAreReady(1);
> {noformat}
> Notably, the {{waitTilGatewaySendersAreReady}} expects to find 1 gateway
> mbean from the two servers on which the gateway will be created.
> However, the underlying implementation of the method expects to find
> *exactly* 1 bean, meaning that if the gateway creation and bean registration
> occurs before the {{wait*}} method is called, the test will fail to a hang
> despite correct execution.
> The true root cause of this error is likely the ambiguity in the method and
> variable naming. Consider renaming this method and related to be explicitly
> clear to future developers that these methods have exact expectation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5295) Improve error reporting in ClusterStartupRule await methods
[ https://issues.apache.org/jira/browse/GEODE-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542299#comment-16542299 ] ASF subversion and git services commented on GEODE-5295: Commit 84e911cb22097319aa1130fdd02a57d0354c9cc4 in geode's branch refs/heads/feature/GEODE-5145 from [~prhomberg] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=84e911c ] GEODE-5295: Improve member WaitUntilX methods (#2039) * Improve error reporting in the event of a WaitUntil timeout. * Renamed methods to avoid future developer error similar to GEODE-5299 > Improve error reporting in ClusterStartupRule await methods > --- > > Key: GEODE-5295 > URL: https://issues.apache.org/jira/browse/GEODE-5295 > Project: Geode > Issue Type: Improvement >Reporter: Patrick Rhomberg >Assignee: Patrick Rhomberg >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > The family of methods that wait until the cluster's gateways / regions / disk > stores are ready will occasionally hang, having a number not equal to the > expected number of beans. In these cases, it unclear if the number of > expected element beans is too few (indicating a delay or failure to start) or > too many (indicating a failure to destroy a previous test). > Failure reporting should be improved to indicate the nature of failure. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5408) Document gfsh remove -all option not avail for partitioned regions
[
https://issues.apache.org/jira/browse/GEODE-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542298#comment-16542298
]
ASF subversion and git services commented on GEODE-5408:
Commit 2e1673b3d347aea542416c736c9c3ab1359dc1ad in geode's branch
refs/heads/feature/GEODE-5145 from Karen Miller
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2e1673b ]
GEODE-5408 Update docs for gfsh remove --all (#2119)
> Document gfsh remove -all option not avail for partitioned regions
> --
>
> Key: GEODE-5408
> URL: https://issues.apache.org/jira/browse/GEODE-5408
> Project: Geode
> Issue Type: Improvement
> Components: docs
>Reporter: Karen Smoler Miller
>Assignee: Karen Smoler Miller
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The command reference page for {{gfsh remove}} in the documentation ought to
> explicitly say that the -all option is not available for partitioned regions.
> The gfsh help text and the error message (if one tries to use the -all
> option do explicitly state this. So, just the docs need updating.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5429) SUPERFLAKY: Multiple failures from RestAPIsWithSSLDUnitTest
Dan Smith created GEODE-5429:
Summary: SUPERFLAKY: Multiple failures from
RestAPIsWithSSLDUnitTest
Key: GEODE-5429
URL: https://issues.apache.org/jira/browse/GEODE-5429
Project: Geode
Issue Type: Task
Reporter: Dan Smith
Several of the test in this class failed multiple times in a pass over 200 runs
of DistributedTest.
{noformat}
16 failures
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSimpleSSLWithMultiKey_KeyStore_WithInvalidClientKey
(94.02985074626866% success rate)
7 failures
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithTLSv12ProtocolLegacy
(97.38805970149254% success rate)
5 failures
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithoutKeyStoreTypeLegacy
(98.13432835820896% success rate)
2 failures
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testWithMultipleProtocol
(99.25373134328358% success rate)
2 failures
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithTLSv11Protocol
(99.25373134328358% success rate)
2 failures
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithMultipleCipherSuite
(99.25373134328358% success rate)
1 failures
org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testWithMultipleProtocolLegacy
(99.6268656716418% success rate)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5394) ClientServerMiscBCDUnitTest.testRegionClose failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542303#comment-16542303
]
ASF subversion and git services commented on GEODE-5394:
Commit 5da7ad4a399135a0910e130f6d202acf0d7a5197 in geode's branch
refs/heads/feature/GEODE-5145 from [~markerichanson]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5da7ad4 ]
GEODE-5394: Change to add additional logging in the event of a failure.
Co-authored-by: Jinmei Liao
> ClientServerMiscBCDUnitTest.testRegionClose failed in CI
>
>
> Key: GEODE-5394
> URL: https://issues.apache.org/jira/browse/GEODE-5394
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available, swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.html
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This test failed in a recent CI run on
> 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
>
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
> testRegionClose[3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest$$Lambda$111/993337154.run
> in VM 2 running on Host fe6abf8a5e6f with 5 VMs
> Caused by:
> java.lang.AssertionError: Event never occurred after 4 ms: null
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-5145) Lucene index needs to support being destroyed while region is being created
[ https://issues.apache.org/jira/browse/GEODE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542304#comment-16542304 ] ASF subversion and git services commented on GEODE-5145: Commit d67979da7c38c38b9509b152421f4eee1468fa57 in geode's branch refs/heads/feature/GEODE-5145 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d67979d ] GEODE-5145: Added support for destroying an index during region creation > Lucene index needs to support being destroyed while region is being created > --- > > Key: GEODE-5145 > URL: https://issues.apache.org/jira/browse/GEODE-5145 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Barry Oglesby >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > Attempting to destroy a lucene index while the region is being created may > leave the lucene service in an inconsistent state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5292) Replace with concurrent clear and destroy leaks off heap memory
[ https://issues.apache.org/jira/browse/GEODE-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542295#comment-16542295 ] ASF subversion and git services commented on GEODE-5292: Commit e4bd46d71d0a8166868fc1505284e31972e1e842 in geode's branch refs/heads/feature/GEODE-5145 from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e4bd46d ] Revert "[GEODE-5292] Actually destroy the region instead of pretending to." This reverts commit 9037d42bf291b504fea98bff4c851aac15e0625c. This commit is causing IntegrationTest to fail in the CI pipeline. > Replace with concurrent clear and destroy leaks off heap memory > --- > > Key: GEODE-5292 > URL: https://issues.apache.org/jira/browse/GEODE-5292 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > For a region that has been configured with off-heap storage and overflow to > disk, memory can be leaked if > * region clear > * region destroy > * region replace > all happen concurrently. The root cause appears to be region clear modifying > entries for values stored on disk without synchronizing the entries. This > prevents replace from freeing the off-heap memory for the new value when the > replace fails because the region is being destroyed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5388) Add a gradle task to run a test N times in parallel
[ https://issues.apache.org/jira/browse/GEODE-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542322#comment-16542322 ] ASF subversion and git services commented on GEODE-5388: Commit 082f1d5619acf5fab93017cc200d58162c7c3021 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=082f1d5 ] GEODE-5388: Adding a gradle task to repeat a test Example ./gradlew repeatTest --tests PartitionedRegionHADUnitTest.testBucketFailOverDuringCacheClose -Prepeat=100 > Add a gradle task to run a test N times in parallel > --- > > Key: GEODE-5388 > URL: https://issues.apache.org/jira/browse/GEODE-5388 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Time Spent: 20m > Remaining Estimate: 0h > > Add a gradle task that can run a given test method N number of times, ideally > in parallel using our docker parallel test execution. > This will be useful for reproducing a bug, and potentially for GEODE-5387 as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5360) AcceptorImpl.close calls shutdownNow, which interrupts threads
[
https://issues.apache.org/jira/browse/GEODE-5360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542346#comment-16542346
]
Dan Smith commented on GEODE-5360:
--
This was fixed by this commit
{noformat}
commit 035e7bb5261da510fea3321379383a86d6a1439b
Author: Dan Smith
Date: Thu Jun 28 11:55:06 2018 -0700
GEM-2031: Removing the use of shutdownNow from AcceptorImpl pools
Using shutdownNow interrupts the threads in these pools. These threads
may be doing IO on sockets, so shutdownNow will interrupt the threads
and potentially cause issues shutting down.
{noformat}
> AcceptorImpl.close calls shutdownNow, which interrupts threads
> --
>
> Key: GEODE-5360
> URL: https://issues.apache.org/jira/browse/GEODE-5360
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Dan Smith
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We saw a hang during close cache where a member was stuck waiting for a
> reply. I tracked it down to the fact that AcceptorImpl.close was calling
> shutdownNow on it's thread pools, and interrupted a clientQueueInitialization
> thread in the middle of a GII. I believe this caused a lost message due to
> GEODE-5358, resulting in a hang.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-567) SUPERFLAKY: FixedPartitioningDUnitTest.testBug43283
[
https://issues.apache.org/jira/browse/GEODE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-567:
Summary: SUPERFLAKY: FixedPartitioningDUnitTest.testBug43283 (was: CI
Failure: FixedPartitioningDUnitTest.testBug43283)
> SUPERFLAKY: FixedPartitioningDUnitTest.testBug43283
> ---
>
> Key: GEODE-567
> URL: https://issues.apache.org/jira/browse/GEODE-567
> Project: Geode
> Issue Type: Bug
> Components: regions
>Reporter: Barry Oglesby
>Priority: Major
> Labels: CI, Flaky, swat
>
> Geode_develop_DistributedTests
> Private Build #571 (Nov 14, 2015 7:09:09 AM)
> Revision: 88da702593157d8a0c014295cab16149fc088dfc
> {noformat}
> junit.framework.AssertionFailedError: exception thrown is not
> PartitionNotAvailableException
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.TestCase.fail(TestCase.java:227)
> at
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:545)
> {noformat}
> Standard Output shows:
> {noformat}
> Previously run tests: [ReliableMessagingDUnitTest,
> CacheServerTransactionsDUnitTest, ForceInvalidateOffHeapEvictionDUnitTest,
> UnregisterInterestDUnitTest, InterestRegrListenerDUnitTest,
> EventIDVerificationDUnitTest, DataSerializerPropogationDUnitTest,
> CacheServerTransactionsSelectorDUnitTest, Bug36805DUnitTest,
> PersistentColocatedPartitionedRegionDUnitTest, Bug51400DUnitTest,
> PersistPRKRFDUnitTest, StreamingPartitionOperationOneDUnitTest,
> Bug47388DUnitTest, PartitionedRegionMetaDataCleanupDUnitTest,
> PersistentPartitionedRegionOldConfigDUnitTest,
> PartitionedRegionLoaderWriterDUnitTest, ElidedPutAllDUnitTest,
> ShutdownAllDUnitTest, Bug39356DUnitTest, PartitionResolverDUnitTest,
> Bug43684DUnitTest, StreamingPartitionOperationManyDUnitTest,
> PersistentPartitionedRegionWithTransactionDUnitTest,
> PersistentPartitionedRegionDUnitTest,
> FixedPartitioningWithColocationAndPersistenceDUnitTest,
> FixedPartitioningDUnitTest]
> {noformat}
> Standard Error shows:
> {noformat}
> dunit.RMIException: While invoking
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningTestBase.putThorughAccessor_Immediate
> in VM 3 running on Host cc4-rh6.gemstone.com with 4 VMs
> at dunit.VM.invoke(VM.java:170)
> at
> com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testBug43283(FixedPartitioningDUnitTest.java:539)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.GeneratedMethodAccessor169.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.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:106)
> at
[jira] [Resolved] (GEODE-4378) PersistentRecoveryOrderDUnitTest testCrashDuringPreparePersistentId fails with IllegalStateException
[
https://issues.apache.org/jira/browse/GEODE-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-4378.
--
Resolution: Duplicate
> PersistentRecoveryOrderDUnitTest testCrashDuringPreparePersistentId fails
> with IllegalStateException
>
>
> Key: GEODE-4378
> URL: https://issues.apache.org/jira/browse/GEODE-4378
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Reporter: Darrel Schneider
>Priority: Minor
> Labels: CI, flaky, swat
>
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> {noformat}
> java.lang.RuntimeException: java.lang.IllegalStateException: Disk store
> PersistentRecoveryOrderDUnitTest_testCrashDuringPreparePersistentIdRegion not
> found
> at
> org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:186)
> at
> org.apache.geode.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> org.apache.geode.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1336)
>
> Caused by:
> java.lang.IllegalStateException: Disk store
> PersistentRecoveryOrderDUnitTest_testCrashDuringPreparePersistentIdRegion not
> found
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-1703) SUPERFLAKY: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1703:
-
Summary: SUPERFLAKY:
PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId (was:
SUPERFLAKY: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId
fails assertion: Region not created within3)
> SUPERFLAKY:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: regions, tests
>Reporter: Kirk Lund
>Priority: Minor
> Labels: CI, flaky, swat
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5412) Shake out additional flaky tests by running DistributedTest many times
[
https://issues.apache.org/jira/browse/GEODE-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-5412.
--
Resolution: Fixed
Results are here:
{noformat}
(concourse) bin> ./concourse_job_performance.py
https://concourse.apachegeode-ci.info mass-dist DistributedTest 300
***
Overall build success rate: 56.343283582089555%
***
org.apache.geode.internal.cache.ClearTXLockingDUnitTest.testPutWithClearDifferentVM:
7 failures (97.38805970149254% success rate)
Failed build 301 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/301
Failed build 295 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/295
Failed build 277 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/277
Failed build 226 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/226
Failed build 182 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/182
Failed build 180 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/180
Failed build 60 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/60
org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator:
81 failures (69.77611940298507% success rate)
Failed build 295 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/295
Failed build 287 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/287
Failed build 286 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/286
Failed build 285 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/285
Failed build 282 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/282
Failed build 277 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/277
Failed build 275 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/275
Failed build 272 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/272
Failed build 267 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/267
Failed build 266 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/266
Failed build 264 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/264
Failed build 262 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/262
Failed build 261 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/261
Failed build 252 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/252
Failed build 251 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/251
Failed build 247 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/247
Failed build 244 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/244
Failed build 239 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/239
Failed build 237 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/237
Failed build 232 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/232
Failed build 230 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/230
Failed build 229 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/229
Failed build 228 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/228
Failed build 226 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/226
Failed build 221 at
https://concourse.apachegeode-ci.info/teams/staging/pipelines/mass-dist/jobs/DistributedTest/builds/221
Failed build 213 at
[jira] [Updated] (GEODE-5097) SUPERFLAKY: AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners
[
https://issues.apache.org/jira/browse/GEODE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5097:
-
Summary: SUPERFLAKY:
AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners (was: CI Failure:
AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners)
> SUPERFLAKY: AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners
>
>
> Key: GEODE-5097
> URL: https://issues.apache.org/jira/browse/GEODE-5097
> Project: Geode
> Issue Type: Bug
>Reporter: Barry Oglesby
>Priority: Major
> Labels: swat
>
> Occurred in FlakyTest 434:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/434
> {noformat}
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest
> > testAsyncStatsTwoListeners FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest$$Lambda$79/2036409943.run
> in VM 2 running on Host 5f4c74fb-2dca-48a0-4b2c-156d54846ff4 with 5 VMs
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
> at
> org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUnitTest.testAsyncStatsTwoListeners(AsyncEventQueueStatsDUnitTest.java:139)
> Caused by:
> org.awaitility.core.ConditionTimeoutException: Condition defined as a lambda
> expression in org.apache.geode.internal.cache.wan.AsyncEventQueueTestBase
> that uses int,
> intorg.apache.geode.cache.asyncqueue.internal.AsyncEventQueueStats Expected
> queue entries: 1000 but actual entries: 999 expected:<1000> but was:<999>
> within 120 seconds.
> at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
> at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:117)
> at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:32)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:809)
> at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:648)
> at
> org.apache.geode.internal.cache.wan.AsyncEventQueueTestBase.checkAsyncEventQueueStats(AsyncEventQueueTestBase.java:735)
> at org.apache.geode.internal.cache.wan.asyncqueue.AsyncEventQueueStatsDUni
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-1703) SUPERFLAKY: PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId
[
https://issues.apache.org/jira/browse/GEODE-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542287#comment-16542287
]
Dan Smith commented on GEODE-1703:
--
Note that this same test case seems to fail for multiple different reasons, the
earlier comments may not be the same as the failures from patricks runs. In any
case, we should fix this test until it passes consistently.
> SUPERFLAKY:
> PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId
> ---
>
> Key: GEODE-1703
> URL: https://issues.apache.org/jira/browse/GEODE-1703
> Project: Geode
> Issue Type: Bug
> Components: regions, tests
>Reporter: Kirk Lund
>Priority: Minor
> Labels: CI, flaky, swat
>
> {noformat}
> :geode-core:distributedTest
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest
> > testCrashDuringPreparePersistentId FAILED
> java.lang.AssertionError: Region not created within3
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase._createPersistentRegion(PersistentReplicatedTestBase.java:179)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentReplicatedTestBase.createPersistentRegion(PersistentReplicatedTestBase.java:172)
> at
> com.gemstone.gemfire.internal.cache.persistence.PersistentRecoveryOrderDUnitTest.testCrashDuringPreparePersistentId(PersistentRecoveryOrderDUnitTest.java:1344)
> 7429 tests completed, 1 failed, 587 skipped
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5429) SUPERFLAKY: Multiple failures from RestAPIsWithSSLDUnitTest
[
https://issues.apache.org/jira/browse/GEODE-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5429:
-
Labels: swat (was: )
> SUPERFLAKY: Multiple failures from RestAPIsWithSSLDUnitTest
> ---
>
> Key: GEODE-5429
> URL: https://issues.apache.org/jira/browse/GEODE-5429
> Project: Geode
> Issue Type: Task
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
>
> Several of the test in this class failed multiple times in a pass over 200
> runs of DistributedTest.
> {noformat}
> 16 failures
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSimpleSSLWithMultiKey_KeyStore_WithInvalidClientKey
> (94.02985074626866% success rate)
> 7 failures
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithTLSv12ProtocolLegacy
> (97.38805970149254% success rate)
> 5 failures
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithoutKeyStoreTypeLegacy
> (98.13432835820896% success rate)
> 2 failures
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testWithMultipleProtocol
> (99.25373134328358% success rate)
> 2 failures
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithTLSv11Protocol
> (99.25373134328358% success rate)
> 2 failures
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testSSLWithMultipleCipherSuite
> (99.25373134328358% success rate)
> 1 failures
> org.apache.geode.rest.internal.web.controllers.RestAPIsWithSSLDUnitTest.testWithMultipleProtocolLegacy
> (99.6268656716418% success rate)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (GEODE-5430) Add getController method to VM
[ https://issues.apache.org/jira/browse/GEODE-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5430: Assignee: Kirk Lund > Add getController method to VM > -- > > Key: GEODE-5430 > URL: https://issues.apache.org/jira/browse/GEODE-5430 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Add getController method to VM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-1866) SUPERFLAKY: LauncherLifecycleCommandsDUnitTest.test014GemFireServerJvmProcessTerminatesOnOutOfMemoryError
[
https://issues.apache.org/jira/browse/GEODE-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-1866:
-
Summary: SUPERFLAKY:
LauncherLifecycleCommandsDUnitTest.test014GemFireServerJvmProcessTerminatesOnOutOfMemoryError
(was:
LauncherLifecycleCommandsDUnitTest.test014GemFireServerJvmProcessTerminatesOnOutOfMemoryError)
> SUPERFLAKY:
> LauncherLifecycleCommandsDUnitTest.test014GemFireServerJvmProcessTerminatesOnOutOfMemoryError
> -
>
> Key: GEODE-1866
> URL: https://issues.apache.org/jira/browse/GEODE-1866
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: xiaojian zhou
>Priority: Major
> Labels: CI, flaky, swat
> Fix For: 1.0.0-incubating
>
>
> {noformat}
> Geode_develop_DistributedTests 3832
> one of failures is:
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest
> > test006StartLocatorInRelativeDirectory FAILED
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.readPid(LauncherLifecycleCommandsDUnitTest.java:175)
> at
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.waitForGemFireProcessToStop(LauncherLifecycleCommandsDUnitTest.java:240)
> at
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.stopLocator(LauncherLifecycleCommandsDUnitTest.java:210)
> at
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.stopLocator(LauncherLifecycleCommandsDUnitTest.java:206)
> at
> com.gemstone.gemfire.management.internal.cli.commands.LauncherLifecycleCommandsDUnitTest.test006StartLocatorInRelativeDirectory(LauncherLifecycleCommandsDUnitTest.java:492)
> [noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5388) Add a gradle task to run a test N times in parallel
[ https://issues.apache.org/jira/browse/GEODE-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5388. -- Resolution: Fixed > Add a gradle task to run a test N times in parallel > --- > > Key: GEODE-5388 > URL: https://issues.apache.org/jira/browse/GEODE-5388 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: pull-request-available, swat > Time Spent: 20m > Remaining Estimate: 0h > > Add a gradle task that can run a given test method N number of times, ideally > in parallel using our docker parallel test execution. > This will be useful for reproducing a bug, and potentially for GEODE-5387 as > well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5431) Improve error message when using DistributedDiskDirRule with VM.bounce()
[ https://issues.apache.org/jira/browse/GEODE-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-5431: Assignee: Kirk Lund > Improve error message when using DistributedDiskDirRule with VM.bounce() > > > Key: GEODE-5431 > URL: https://issues.apache.org/jira/browse/GEODE-5431 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > VM.bounce() ignores all rules. DistributedDiskDirRule tearDown throws NPE if > invoked within a dunit VM that didn't perform setUp. I'd like to improve the > error message. > Eventually, we should fix VM.bounce() to invoke setUp of all distributed > rules within the new VM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5431) Improve error message when using DistributedDiskDirRule with VM.bounce()
Kirk Lund created GEODE-5431: Summary: Improve error message when using DistributedDiskDirRule with VM.bounce() Key: GEODE-5431 URL: https://issues.apache.org/jira/browse/GEODE-5431 Project: Geode Issue Type: Improvement Components: tests Reporter: Kirk Lund VM.bounce() ignores all rules. DistributedDiskDirRule tearDown throws NPE if invoked within a dunit VM that didn't perform setUp. I'd like to improve the error message. Eventually, we should fix VM.bounce() to invoke setUp of all distributed rules within the new VM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5394) ClientServerMiscBCDUnitTest.testRegionClose failed in CI
[
https://issues.apache.org/jira/browse/GEODE-5394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542263#comment-16542263
]
ASF subversion and git services commented on GEODE-5394:
Commit 5da7ad4a399135a0910e130f6d202acf0d7a5197 in geode's branch
refs/heads/develop from [~markerichanson]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=5da7ad4 ]
GEODE-5394: Change to add additional logging in the event of a failure.
Co-authored-by: Jinmei Liao
> ClientServerMiscBCDUnitTest.testRegionClose failed in CI
>
>
> Key: GEODE-5394
> URL: https://issues.apache.org/jira/browse/GEODE-5394
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Mark Hanson
>Priority: Major
> Labels: pull-request-available, swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest.html
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This test failed in a recent CI run on
> 10d8dabdfa39dde490ae2ebf7a5ece4786cea661
>
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscBCDUnitTest >
> testRegionClose[3] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.ClientServerMiscDUnitTest$$Lambda$111/993337154.run
> in VM 2 running on Host fe6abf8a5e6f with 5 VMs
> Caused by:
> java.lang.AssertionError: Event never occurred after 4 ms: null
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5428) SUPERFLAKY: DurableClientTestCase.testDurableHAFailover
[
https://issues.apache.org/jira/browse/GEODE-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5428:
-
Attachment: Test results - Class
org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.html
> SUPERFLAKY: DurableClientTestCase.testDurableHAFailover
> ---
>
> Key: GEODE-5428
> URL: https://issues.apache.org/jira/browse/GEODE-5428
> Project: Geode
> Issue Type: Task
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.html
>
>
> This test failed frequently over many 200+ runs of DistributedTest. It looks
> like this test was reenabled recently, See GEODE-3721.
> {noformat}
> 23 failures
> org.apache.geode.internal.cache.tier.sockets.DurableClientCrashDUnitTest.testDurableHAFailover
> (91.4179104477612% success rate)
> 19 failures
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.testDurableHAFailover
> (92.91044776119402% success rate)
> 2 failures
> org.apache.geode.internal.cache.tier.sockets.DurableClientSimpleDUnitTest.testDurableHAFailover
> (99.25373134328358% success rate)
> {noformat}
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase >
> testDurableHAFailover FAILED
>
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase$57.run in
> VM 2 running on Host 70293b28b05f with 4 VMs
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
>
> at
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.checkPrimaryRecovery(DurableClientTestCase.java:1732)
>
> at
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.durableFailover(DurableClientTestCase.java:1247)
>
> at
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.testDurableHAFailover(DurableClientTestCase.java:1102)
>
>
> Caused by:
>
> java.lang.AssertionError: Event never occurred after 3 ms: Did
> not detect primary recovery event during wait period
>
> at org.junit.Assert.fail(Assert.java:88)
>
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
>
> at
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase$57.run2(DurableClientTestCase.java:1746)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5428) SUPERFLAKY: DurableClientTestCase.testDurableHAFailover
[
https://issues.apache.org/jira/browse/GEODE-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5428:
-
Labels: swat (was: )
> SUPERFLAKY: DurableClientTestCase.testDurableHAFailover
> ---
>
> Key: GEODE-5428
> URL: https://issues.apache.org/jira/browse/GEODE-5428
> Project: Geode
> Issue Type: Task
>Reporter: Dan Smith
>Priority: Major
> Labels: swat
> Attachments: Test results - Class
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.html
>
>
> This test failed frequently over many 200+ runs of DistributedTest. It looks
> like this test was reenabled recently, See GEODE-3721.
> {noformat}
> 23 failures
> org.apache.geode.internal.cache.tier.sockets.DurableClientCrashDUnitTest.testDurableHAFailover
> (91.4179104477612% success rate)
> 19 failures
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.testDurableHAFailover
> (92.91044776119402% success rate)
> 2 failures
> org.apache.geode.internal.cache.tier.sockets.DurableClientSimpleDUnitTest.testDurableHAFailover
> (99.25373134328358% success rate)
> {noformat}
> {noformat}
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase >
> testDurableHAFailover FAILED
>
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase$57.run in
> VM 2 running on Host 70293b28b05f with 4 VMs
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
>
> at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
>
> at
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.checkPrimaryRecovery(DurableClientTestCase.java:1732)
>
> at
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.durableFailover(DurableClientTestCase.java:1247)
>
> at
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.testDurableHAFailover(DurableClientTestCase.java:1102)
>
>
> Caused by:
>
> java.lang.AssertionError: Event never occurred after 3 ms: Did
> not detect primary recovery event during wait period
>
> at org.junit.Assert.fail(Assert.java:88)
>
> at
> org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
>
> at
> org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase$57.run2(DurableClientTestCase.java:1746)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-5428) SUPERFLAKY: DurableClientTestCase.testDurableHAFailover
Dan Smith created GEODE-5428:
Summary: SUPERFLAKY: DurableClientTestCase.testDurableHAFailover
Key: GEODE-5428
URL: https://issues.apache.org/jira/browse/GEODE-5428
Project: Geode
Issue Type: Task
Reporter: Dan Smith
This test failed frequently over many 200+ runs of DistributedTest. It looks
like this test was reenabled recently, See GEODE-3721.
{noformat}
23 failures
org.apache.geode.internal.cache.tier.sockets.DurableClientCrashDUnitTest.testDurableHAFailover
(91.4179104477612% success rate)
19 failures
org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.testDurableHAFailover
(92.91044776119402% success rate)
2 failures
org.apache.geode.internal.cache.tier.sockets.DurableClientSimpleDUnitTest.testDurableHAFailover
(99.25373134328358% success rate)
{noformat}
{noformat}
org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase >
testDurableHAFailover FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase$57.run in VM
2 running on Host 70293b28b05f with 4 VMs
at org.apache.geode.test.dunit.VM.invoke(VM.java:436)
at org.apache.geode.test.dunit.VM.invoke(VM.java:405)
at org.apache.geode.test.dunit.VM.invoke(VM.java:348)
at
org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.checkPrimaryRecovery(DurableClientTestCase.java:1732)
at
org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.durableFailover(DurableClientTestCase.java:1247)
at
org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase.testDurableHAFailover(DurableClientTestCase.java:1102)
Caused by:
java.lang.AssertionError: Event never occurred after 3 ms: Did not
detect primary recovery event during wait period
at org.junit.Assert.fail(Assert.java:88)
at org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190)
at
org.apache.geode.internal.cache.tier.sockets.DurableClientTestCase$57.run2(DurableClientTestCase.java:1746)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-5325) SUPERFLAKY: PersistentPartitionedRegionDistributedTest.recoversFromCloseDuringRegionOperation fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith updated GEODE-5325:
-
Summary: SUPERFLAKY:
PersistentPartitionedRegionDistributedTest.recoversFromCloseDuringRegionOperation
fails intermittently (was: CI failure:
PersistentPartitionedRegionDistributedTest.recoversFromCloseDuringRegionOperation
fails intermittently)
> SUPERFLAKY:
> PersistentPartitionedRegionDistributedTest.recoversFromCloseDuringRegionOperation
> fails intermittently
> --
>
> Key: GEODE-5325
> URL: https://issues.apache.org/jira/browse/GEODE-5325
> Project: Geode
> Issue Type: Bug
> Components: persistence
>Affects Versions: 1.7.0
>Reporter: Kirk Lund
>Priority: Minor
> Labels: CI, Flaky, swat
>
> {noformat}
> org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionDistributedTest
> > recoversFromCloseDuringRegionOperation FAILED
> java.lang.AssertionError: An exception occurred during asynchronous
> invocation.
> at
> org.apache.geode.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:150)
> at
> org.apache.geode.test.dunit.AsyncInvocation.get(AsyncInvocation.java:424)
> at
> org.apache.geode.test.dunit.AsyncInvocation.get(AsyncInvocation.java:393)
> at
> org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionDistributedTest.recoversFromCloseDuringRegionOperation(PersistentPartitionedRegionDistributedTest.java:999)
> Caused by:
> org.apache.geode.distributed.DistributedSystemDisconnectedException:
> Distribution manager on 172.17.0.4(172):32770 started at Wed Jun 13
> 23:12:28 UTC 2018: Message distribution has terminated
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$Stopper.generateCancelledException(ClusterDistributionManager.java:4556)
> at
> org.apache.geode.distributed.internal.InternalDistributedSystem$Stopper.generateCancelledException(InternalDistributedSystem.java:962)
> at
> org.apache.geode.internal.cache.GemFireCacheImpl$Stopper.generateCancelledException(GemFireCacheImpl.java:1556)
> at
> org.apache.geode.CancelCriterion.checkCancelInProgress(CancelCriterion.java:83)
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7419)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2735)
> at
> org.apache.geode.internal.cache.PartitionedRegion.checkShutdown(PartitionedRegion.java:1745)
> at
> org.apache.geode.internal.cache.PartitionedRegion.putInBucket(PartitionedRegion.java:2972)
> at
> org.apache.geode.internal.cache.PartitionedRegion.virtualPut(PartitionedRegion.java:2091)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:152)
> at
> org.apache.geode.internal.cache.LocalRegion.basicPut(LocalRegion.java:5086)
> at
> org.apache.geode.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1618)
> at
> org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1605)
> at
> org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:413)
> at
> org.apache.geode.internal.cache.partitioned.PersistentPartitionedRegionDistributedTest.lambda$recoversFromCloseDuringRegionOperation$1509c1f8$1(PersistentPartitionedRegionDistributedTest.java:969)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-5392) Cleanup javadocs and code style in AsyncInvocation
[ https://issues.apache.org/jira/browse/GEODE-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5392. -- Resolution: Fixed Fix Version/s: 1.7.0 > Cleanup javadocs and code style in AsyncInvocation > -- > > Key: GEODE-5392 > URL: https://issues.apache.org/jira/browse/GEODE-5392 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Fix For: 1.7.0 > > > Cleanup javadocs and code style in AsyncInvocation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5145) Lucene index needs to support being destroyed while region is being created
[ https://issues.apache.org/jira/browse/GEODE-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542337#comment-16542337 ] ASF subversion and git services commented on GEODE-5145: Commit d9d691f77571180c8098c48a7078bc279b429e98 in geode's branch refs/heads/feature/GEODE-5145 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d9d691f ] GEODE-5145: Updated to version 1.8 > Lucene index needs to support being destroyed while region is being created > --- > > Key: GEODE-5145 > URL: https://issues.apache.org/jira/browse/GEODE-5145 > Project: Geode > Issue Type: Bug > Components: lucene >Reporter: Barry Oglesby >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > > Attempting to destroy a lucene index while the region is being created may > leave the lucene service in an inconsistent state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5391) Fix toString of RegionVersionHolder
[ https://issues.apache.org/jira/browse/GEODE-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5391. -- Resolution: Fixed Fix Version/s: 1.7.0 > Fix toString of RegionVersionHolder > --- > > Key: GEODE-5391 > URL: https://issues.apache.org/jira/browse/GEODE-5391 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Fix For: 1.7.0 > > > The closing "}" is missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5398) Cleanup code and add unit tests for Backups
[ https://issues.apache.org/jira/browse/GEODE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5398. -- Resolution: Fixed Fix Version/s: 1.7.0 > Cleanup code and add unit tests for Backups > --- > > Key: GEODE-5398 > URL: https://issues.apache.org/jira/browse/GEODE-5398 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Some of the Backup classes are lacking unit tests including BackupOperation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5390) Move inner classes to end of persistence impl classes
[ https://issues.apache.org/jira/browse/GEODE-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-5390. -- Resolution: Fixed Fix Version/s: 1.7.0 > Move inner classes to end of persistence impl classes > - > > Key: GEODE-5390 > URL: https://issues.apache.org/jira/browse/GEODE-5390 > Project: Geode > Issue Type: Improvement > Components: persistence >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Move inner classes to end of DiskInitFile, Oplog, DiskInitFileParser. Add > @Override where appropriate. > Improve trace level log statement in Oplog. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5014) Replace org.json with Jackson in geode-assembly
[ https://issues.apache.org/jira/browse/GEODE-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5014: -- Labels: pull-request-available (was: ) > Replace org.json with Jackson in geode-assembly > --- > > Key: GEODE-5014 > URL: https://issues.apache.org/jira/browse/GEODE-5014 > Project: Geode > Issue Type: Sub-task > Components: management, tests >Reporter: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3530) All DistributedTests that extend CliCommandTestBase are Flaky
[ https://issues.apache.org/jira/browse/GEODE-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinmei Liao updated GEODE-3530: --- Description: All DistributedTests that extend CliCommandTestBase are Flaky. The tests need to be rewritten with GfshShellConnectionRule so we can delete CliCommandTestBase. List of test classes extending CliCommandTestBase and existing Flaky tickets: * -AlterRegionCommandDUnitTest- (GEODE-3018) * -ClusterConfigurationDUnitTest- (GEODE-1333, GEODE-1334) * -ConfigCommandsDUnitTest- (GEODE-1449) * -ConnectCommandWithHttpAndSSLDUnitTest- * -CreateAlterDestroyRegionCommandsDUnitTest- (GEODE-973, GEODE-2009, GEODE-3018) * -CreateRegionCommandDUnitTest- (GEODE-973) * -DescribeClientCommandDUnitTest- (GEODE-910) * -DestroyRegionCommandDUnitTest- * -DiskStoreCommandsDUnitTest- (GEODE-1206, GEODE-1406, GEODE-2102) * -DurableClientCommandsDUnitTest- (GEODE-1705, GEODE-3404, GEODE-3359) * -FunctionCommandsDUnitTest- (GEODE-1563) * -GemfireDataCommandsDUnitTest- (GEODE-1182, GEODE-1249, GEODE-1404, GEODE-1430, GEODE-1487, GEODE-1496, GEODE-1561, GEODE-1822, GEODE-2006) * -GetCommandOnRegionWithCacheLoaderDuringCacheMissDUnitTest- (Does not exist) * LauncherLifecycleCommandsDUnitTest * -ListAndDescribeDiskStoreCommandsDUnitTest (does not exist)- * ListClientCommandDUnitTest (GEODE-908) (Jinmei/Finn) * -ListIndexCommandDUnitTest- * -LuceneIndexCommandsDUnitTest- (does not exist) * -MiscellaneousCommandsDUnitTest (GEODE-1034, GEODE-1385, GEODE-1518, GEODE-1605, GEODE-1706, GEODE-2126)- * -QueueCommandsDUnitTest- (does not exist) (GEODE-1429, GEODE-1976) * RebalanceCommandDistributedTest (Finn) * RebalanceCommandOverHttpDistributedTest (Finn) * ShellCommandsDUnitTest (GEODE-989) * -ShowMetricsDUnitTest- (GEODE-1764) * -ShowStackTraceDUnitTest- (does not exist) * -WANCommandTestBase- (and subclasses) * ClientCommandsTestUtils Test classes that *use* but do not extend CliCommandTestBase: * CommandOverrHttpDUnitTest was: All DistributedTests that extend CliCommandTestBase are Flaky. The tests need to be rewritten with GfshShellConnectionRule so we can delete CliCommandTestBase. List of test classes extending CliCommandTestBase and existing Flaky tickets: * -AlterRegionCommandDUnitTest- (GEODE-3018) * -ClusterConfigurationDUnitTest- (GEODE-1333, GEODE-1334) * -ConfigCommandsDUnitTest- (GEODE-1449) * -ConnectCommandWithHttpAndSSLDUnitTest- * -CreateAlterDestroyRegionCommandsDUnitTest- (GEODE-973, GEODE-2009, GEODE-3018) * -CreateRegionCommandDUnitTest- (GEODE-973) * -DescribeClientCommandDUnitTest- (GEODE-910) * -DestroyRegionCommandDUnitTest- * -DiskStoreCommandsDUnitTest- (GEODE-1206, GEODE-1406, GEODE-2102) * -DurableClientCommandsDUnitTest- (GEODE-1705, GEODE-3404, GEODE-3359) * -FunctionCommandsDUnitTest- (GEODE-1563) * -GemfireDataCommandsDUnitTest- (GEODE-1182, GEODE-1249, GEODE-1404, GEODE-1430, GEODE-1487, GEODE-1496, GEODE-1561, GEODE-1822, GEODE-2006) * -GetCommandOnRegionWithCacheLoaderDuringCacheMissDUnitTest- (Does not exist) * LauncherLifecycleCommandsDUnitTest * -ListAndDescribeDiskStoreCommandsDUnitTest (does not exist)- * ListClientCommandDUnitTest (GEODE-908) (Jinmei/Finn) * -ListIndexCommandDUnitTest- * -LuceneIndexCommandsDUnitTest- (does not exist) * -MiscellaneousCommandsDUnitTest (GEODE-1034, GEODE-1385, GEODE-1518, GEODE-1605, GEODE-1706, GEODE-2126)- * -QueueCommandsDUnitTest- (does not exist) (GEODE-1429, GEODE-1976) * RebalanceCommandDistributedTest * RebalanceCommandOverHttpDistributedTest * ShellCommandsDUnitTest (GEODE-989) * -ShowMetricsDUnitTest- (GEODE-1764) * -ShowStackTraceDUnitTest- (does not exist) * -WANCommandTestBase- (and subclasses) * ClientCommandsTestUtils Test classes that *use* but do not extend CliCommandTestBase: * CommandOverrHttpDUnitTest > All DistributedTests that extend CliCommandTestBase are Flaky > - > > Key: GEODE-3530 > URL: https://issues.apache.org/jira/browse/GEODE-3530 > Project: Geode > Issue Type: Bug > Components: management, tests >Reporter: Kirk Lund >Assignee: Jinmei Liao >Priority: Major > Labels: CliCommandTestBase, DistributedTest, Flaky, > pull-request-available, swat > Time Spent: 1h > Remaining Estimate: 0h > > All DistributedTests that extend CliCommandTestBase are Flaky. The tests need > to be rewritten with GfshShellConnectionRule so we can delete > CliCommandTestBase. > List of test classes extending CliCommandTestBase and existing Flaky tickets: > * -AlterRegionCommandDUnitTest- (GEODE-3018) > * -ClusterConfigurationDUnitTest- (GEODE-1333, GEODE-1334) > * -ConfigCommandsDUnitTest- (GEODE-1449) > * -ConnectCommandWithHttpAndSSLDUnitTest- > * -CreateAlterDestroyRegionCommandsDUnitTest- (GEODE-973,
[jira] [Created] (GEODE-5423) Improve Gradle configuration performance
Robert Houghton created GEODE-5423: -- Summary: Improve Gradle configuration performance Key: GEODE-5423 URL: https://issues.apache.org/jira/browse/GEODE-5423 Project: Geode Issue Type: Improvement Components: build Reporter: Robert Houghton Clean builds spend minutes of time doing download and unzip of old Geode builds during `configure` step of Gradle. Moving this to the `execute` step allows other tasks to run in parallel, and allows caching of the dependency, instead of checking its existence on every build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
