[jira] [Assigned] (GEODE-3451) Data inconsistency detected in distributed ack test on empty region
[ https://issues.apache.org/jira/browse/GEODE-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-3451: Assignee: Dan Smith > Data inconsistency detected in distributed ack test on empty region > --- > > Key: GEODE-3451 > URL: https://issues.apache.org/jira/browse/GEODE-3451 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Nick Reich >Assignee: Dan Smith >Priority: Major > Labels: ci, flaky, swat > > {noformat} > org.apache.geode.cache30.DistributedAckRegionCCEOffHeapDUnitTest > > testConcurrentEventsOnEmptyRegion FAILED > org.junit.ComparisonFailure: region contents are not consistent for > cckey8 expected: but was: > {noformat} > Note: test failure was not readily reproduced -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-3451) Data inconsistency detected in distributed ack test on empty region
[ https://issues.apache.org/jira/browse/GEODE-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-3451: Assignee: Mark Hanson (was: Dan Smith) > Data inconsistency detected in distributed ack test on empty region > --- > > Key: GEODE-3451 > URL: https://issues.apache.org/jira/browse/GEODE-3451 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Nick Reich >Assignee: Mark Hanson >Priority: Major > Labels: ci, flaky, swat > > {noformat} > org.apache.geode.cache30.DistributedAckRegionCCEOffHeapDUnitTest > > testConcurrentEventsOnEmptyRegion FAILED > org.junit.ComparisonFailure: region contents are not consistent for > cckey8 expected: but was: > {noformat} > Note: test failure was not readily reproduced -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5476) Change pipeline to run all tests in external instances for performance
[ https://issues.apache.org/jira/browse/GEODE-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562105#comment-16562105 ] ASF subversion and git services commented on GEODE-5476: Commit 3e8a9368f58256eb39b79881bf7abd9fe2f5f5f5 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3e8a936 ] GEODE-5476: Reduce build output while preserving some sense of progress. (#) > Change pipeline to run all tests in external instances for performance > -- > > Key: GEODE-5476 > URL: https://issues.apache.org/jira/browse/GEODE-5476 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5464) Add generics to DistributionManager
[ https://issues.apache.org/jira/browse/GEODE-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562113#comment-16562113 ] ASF subversion and git services commented on GEODE-5464: Commit 58715ac2f0bb086c577d204131c129a4338b07c9 in geode's branch refs/heads/develop from [~gosullivan] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=58715ac ] GEODE-5464: Generify DistributionManager and related classes (#2174) GEODE-5464: Generify DistributionManager and related classes * Augment various collections to use generics * Inline some iterator loops that were trivially "foreach" loops * remove unused code * Inline some redundant local variables * make some methods more private * change some tests to use `InternalDistributedMember` instead of `DistributedMember`. * Make ThrottlingMemLinkedQueueWithDMStats generic and use atomic. - The previous synchronization looked quite wrong. > Add generics to DistributionManager > --- > > Key: GEODE-5464 > URL: https://issues.apache.org/jira/browse/GEODE-5464 > Project: Geode > Issue Type: Bug > Components: membership, messaging >Reporter: Galen O'Sullivan >Assignee: Galen O'Sullivan >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > DistributionManager has a number of methods that take/return various > {{Collection}} types without specifying the types of the elements in the > collection. This code would be significantly more readable and understandable > if generics were added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5464) Add generics to DistributionManager
[ https://issues.apache.org/jira/browse/GEODE-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562112#comment-16562112 ] ASF subversion and git services commented on GEODE-5464: Commit 58715ac2f0bb086c577d204131c129a4338b07c9 in geode's branch refs/heads/develop from [~gosullivan] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=58715ac ] GEODE-5464: Generify DistributionManager and related classes (#2174) GEODE-5464: Generify DistributionManager and related classes * Augment various collections to use generics * Inline some iterator loops that were trivially "foreach" loops * remove unused code * Inline some redundant local variables * make some methods more private * change some tests to use `InternalDistributedMember` instead of `DistributedMember`. * Make ThrottlingMemLinkedQueueWithDMStats generic and use atomic. - The previous synchronization looked quite wrong. > Add generics to DistributionManager > --- > > Key: GEODE-5464 > URL: https://issues.apache.org/jira/browse/GEODE-5464 > Project: Geode > Issue Type: Bug > Components: membership, messaging >Reporter: Galen O'Sullivan >Assignee: Galen O'Sullivan >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > DistributionManager has a number of methods that take/return various > {{Collection}} types without specifying the types of the elements in the > collection. This code would be significantly more readable and understandable > if generics were added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5443) Stop the UITests pipeline from automatically running.
[ https://issues.apache.org/jira/browse/GEODE-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562123#comment-16562123 ] ASF subversion and git services commented on GEODE-5443: Commit 82a5fe6342113cacfdcc3002015a8e6a18e02cf7 in geode's branch refs/heads/develop from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=82a5fe6 ] GEODE-5443: removing uiTests from the CI > Stop the UITests pipeline from automatically running. > - > > Key: GEODE-5443 > URL: https://issues.apache.org/jira/browse/GEODE-5443 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: pull-request-available, swat > Time Spent: 2h 20m > Remaining Estimate: 0h > > The UI Tests are flaky, so we don't want to automatically run it anymore. We > want to manually run it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5443) Stop the UITests pipeline from automatically running.
[ https://issues.apache.org/jira/browse/GEODE-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-5443. -- Resolution: Fixed > Stop the UITests pipeline from automatically running. > - > > Key: GEODE-5443 > URL: https://issues.apache.org/jira/browse/GEODE-5443 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: pull-request-available, swat > Time Spent: 2h 20m > Remaining Estimate: 0h > > The UI Tests are flaky, so we don't want to automatically run it anymore. We > want to manually run it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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 ] Dan Smith reassigned GEODE-3530: Assignee: Helena Bales > 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: Helena Bales >Priority: Major > Labels: CliCommandTestBase, DistributedTest, Flaky, > pull-request-available, swat > Time Spent: 5h 50m > 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, 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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4934) CI Failure: GfshScript timing out intermittently waiting for execution to complete
[ https://issues.apache.org/jira/browse/GEODE-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-4934: Assignee: (was: Kenneth Howe) > CI Failure: GfshScript timing out intermittently waiting for execution to > complete > -- > > Key: GEODE-4934 > URL: https://issues.apache.org/jira/browse/GEODE-4934 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.5.0 >Reporter: Kenneth Howe >Priority: Major > Labels: CI, pull-request-available, swat > Time Spent: 40m > Remaining Estimate: 0h > > GfshScript.awaitIfNecessary native method call to determine if the process > executing the script is alive hangs. This is not a hard failure, but it can > be reproduced with frequently running selected tests from command line. This > following set of tests produces failures when run on a Linux host (tested on > CentOS 7). > {code} > ./gradlew clean geode-lucene:precheckin --parallel -x rat -x javadoc -x > spotlessCheck{code} > {code} > {code:title=Typical failure stack} > org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest > > cannotStopServerByNameWhenNotConnected FAILED > org.junit.ComparisonFailure: expected:<[0]> but was:<[1]> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.test.junit.rules.gfsh.GfshScript.awaitIfNecessary(GfshScript.java:116) > at > org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98) > at > org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:87) > at > org.apache.geode.management.internal.cli.commands.StopServerAcceptanceTest.startCluster(StopServerAcceptanceTest.java:35) > {code} > All failures show the same stack from {{at > org.apache.geode.test.junit.rules.gfsh.GfshRule.execute(GfshRule.java:98)}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5387) Add job to precheckin pipeline to run new or modified tests N times
[ https://issues.apache.org/jira/browse/GEODE-5387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-5387: Assignee: (was: Dan Smith) > Add job to precheckin pipeline to run new or modified tests N times > --- > > Key: GEODE-5387 > URL: https://issues.apache.org/jira/browse/GEODE-5387 > Project: Geode > Issue Type: Task > Components: tests >Reporter: Dan Smith >Priority: Major > Labels: swat > > Add a job to the concourse precheckin pipeline to identify dunit tests that > are newly introduced or modified and run these tests multiple times. > We should have a limit on the number of tests to run, if a diff changes more > than X tests we will not run the additional tests. > The intent is to prevent people from introducing new flaky tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5410) Throw KeyNotFoundException occurs when using MSTest with NativeClient
[ https://issues.apache.org/jira/browse/GEODE-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison resolved GEODE-5410. Resolution: Workaround > Throw KeyNotFoundException occurs when using MSTest with NativeClient > - > > Key: GEODE-5410 > URL: https://issues.apache.org/jira/browse/GEODE-5410 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Masaki Yamakawa >Assignee: Addison >Priority: Minor > > > {code:java} > Exception while receiving subscription event for endpoint > {host}:40404::apache::geode::client::Exception:GFCLI_EXCEPTION:System.Collections.Generic.KeyNotFoundException: > 指定されたキーはディレクトリ内に存在しませんでした。 > 場所 System.ThrowHelper.ThrowKeyNotFoundException() > 場所 System.Collections.Generic.Dictionary`2.get_Item(TKey key) > 場所 > apache.geode.client.ManagedCacheableKeyBytesGeneric.fromData(ManagedCacheableKeyBytesGeneric* > , DataInput* input){code} > NOTE: appdomain-enabled is set to true. > NOTE: In NUnit, this error is solved by setting appdomain-enabled to true. > I created a simple application to confirm this issue. > It exists in the following: > [https://github.com/masaki-yamakawa/GeodeNativeSample] > # Build with java and create a jar file. > # Start Locator with gfsh. > # Start CacheServer with gfsh. (start server -name=\{Name} > --classpath=\{Path}/GeodeNativeSample-1.0.jar) > # Build C#. > # Execute C# UnitTestProject1 with VSTest.Console.exe. (VSTest.Console.exe > UnitTestProject1.dll) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5410) Throw KeyNotFoundException occurs when using MSTest with NativeClient
[ https://issues.apache.org/jira/browse/GEODE-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562156#comment-16562156 ] Addison commented on GEODE-5410: [~masaki.yamakawa], try disabling app domains in XUnit. [https://stackoverflow.com/questions/2849246/static-and-default-constructor] [https://xunit.github.io/docs/configuring-with-json] In future releases of Geode, this will not be a problem in Geode Native because we moved away from a static client cache. > Throw KeyNotFoundException occurs when using MSTest with NativeClient > - > > Key: GEODE-5410 > URL: https://issues.apache.org/jira/browse/GEODE-5410 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Masaki Yamakawa >Assignee: Addison >Priority: Minor > > > {code:java} > Exception while receiving subscription event for endpoint > {host}:40404::apache::geode::client::Exception:GFCLI_EXCEPTION:System.Collections.Generic.KeyNotFoundException: > 指定されたキーはディレクトリ内に存在しませんでした。 > 場所 System.ThrowHelper.ThrowKeyNotFoundException() > 場所 System.Collections.Generic.Dictionary`2.get_Item(TKey key) > 場所 > apache.geode.client.ManagedCacheableKeyBytesGeneric.fromData(ManagedCacheableKeyBytesGeneric* > , DataInput* input){code} > NOTE: appdomain-enabled is set to true. > NOTE: In NUnit, this error is solved by setting appdomain-enabled to true. > I created a simple application to confirm this issue. > It exists in the following: > [https://github.com/masaki-yamakawa/GeodeNativeSample] > # Build with java and create a jar file. > # Start Locator with gfsh. > # Start CacheServer with gfsh. (start server -name=\{Name} > --classpath=\{Path}/GeodeNativeSample-1.0.jar) > # Build C#. > # Execute C# UnitTestProject1 with VSTest.Console.exe. (VSTest.Console.exe > UnitTestProject1.dll) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5450) Creating a JNDI binding w/o a username or password leads to NullPointerException
[ https://issues.apache.org/jira/browse/GEODE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil Bawaskar resolved GEODE-5450. - Resolution: Fixed Fix Version/s: 1.7.0 > Creating a JNDI binding w/o a username or password leads to > NullPointerException > > > Key: GEODE-5450 > URL: https://issues.apache.org/jira/browse/GEODE-5450 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Bradford D. Boyle >Assignee: Benjamin P Ross >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > If a user creates a JNDI binding through gfsh and they omit either the > username or password, then they will get a `NullPointerException` when they > try to get a JDBC connection. > > Here is a stack trace: > {code} > java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:460) > at > org.apache.geode.internal.datasource.GemFireBasicDataSource.getConnection(GemFireBasicDataSource.java:94) > at > io.pivotal.gemfire.PostgresVersionFunction.execute(PostgresVersionFunction.java:33) > at > org.apache.geode.internal.cache.execute.AbstractExecution.executeFunctionLocally(AbstractExecution.java:333) > at > org.apache.geode.internal.cache.execute.AbstractExecution$2.run(AbstractExecution.java:302) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1121) > at > org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:109) > at > org.apache.geode.distributed.internal.ClusterDistributionManager$9$1.run(ClusterDistributionManager.java:990) > at java.lang.Thread.run(Thread.java:748) > {code} > You can reproduce this with the following function: > {code:language=java} > public class PostgresVersionFunction implements Function { > @Override > public void execute(FunctionContext context) { > String[] arguments = (String[]) context.getArguments(); > String dataSourceName = arguments[0]; > LogManager.getLogger().info("[datasource=" + > context.getArguments()+"]"); > Context ctx = JNDIInvoker.getJNDIContext(); > DataSource dataSource; > try { > dataSource = (DataSource) ctx.lookup("java:/" + dataSourceName); > } catch (Exception e) { > // TODO exception handling. > LogManager.getLogger().error(e.getMessage(), e); > context.getResultSender().lastResult(e); > return; > } > try (Connection connection = dataSource.getConnection(); > Statement statement = connection.createStatement() > ) { > ResultSet resultSet = statement.executeQuery("SELECT VERSION();"); > resultSet.next(); > context.getResultSender().lastResult(resultSet.getString(1)); > } catch (SQLException e) { > context.getResultSender().lastResult(e); > } > } > } > {code} > and the following gfsh commands: > {code} > start locator --name=locator --include-system-classpath > start server --name=server1 --include-system-classpath > deploy --jar=/root/gemfire-greenplum/simple-function.jar > create jndi-binding --name=datasource --type=SIMPLE > --jdbc-driver-class="org.postgresql.Driver" > --connection-url="jdbc:postgresql://localhost:5432/gpadmin" > execute function --id=io.pivotal.gemfire.PostgresVersionFunction > --arguments=datasource > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-5410) Throw KeyNotFoundException occurs when using MSTest with NativeClient
[ https://issues.apache.org/jira/browse/GEODE-5410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Addison closed GEODE-5410. -- > Throw KeyNotFoundException occurs when using MSTest with NativeClient > - > > Key: GEODE-5410 > URL: https://issues.apache.org/jira/browse/GEODE-5410 > Project: Geode > Issue Type: Bug > Components: native client >Reporter: Masaki Yamakawa >Assignee: Addison >Priority: Minor > > > {code:java} > Exception while receiving subscription event for endpoint > {host}:40404::apache::geode::client::Exception:GFCLI_EXCEPTION:System.Collections.Generic.KeyNotFoundException: > 指定されたキーはディレクトリ内に存在しませんでした。 > 場所 System.ThrowHelper.ThrowKeyNotFoundException() > 場所 System.Collections.Generic.Dictionary`2.get_Item(TKey key) > 場所 > apache.geode.client.ManagedCacheableKeyBytesGeneric.fromData(ManagedCacheableKeyBytesGeneric* > , DataInput* input){code} > NOTE: appdomain-enabled is set to true. > NOTE: In NUnit, this error is solved by setting appdomain-enabled to true. > I created a simple application to confirm this issue. > It exists in the following: > [https://github.com/masaki-yamakawa/GeodeNativeSample] > # Build with java and create a jar file. > # Start Locator with gfsh. > # Start CacheServer with gfsh. (start server -name=\{Name} > --classpath=\{Path}/GeodeNativeSample-1.0.jar) > # Build C#. > # Execute C# UnitTestProject1 with VSTest.Console.exe. (VSTest.Console.exe > UnitTestProject1.dll) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5495) Double decrement of HAEventWrapper ref count due to race between QRM and DestroyRQ
Ryan McMahon created GEODE-5495: --- Summary: Double decrement of HAEventWrapper ref count due to race between QRM and DestroyRQ Key: GEODE-5495 URL: https://issues.apache.org/jira/browse/GEODE-5495 Project: Geode Issue Type: Bug Components: client queues Reporter: Ryan McMahon Fix For: 1.8.0 When a client disconnects due to network issues e.g. SocketTimeoutExceptions we will destroy the HARegionQueue for that client. As part of that process, we decrement the reference count on the HAEventWrappers used by that client in the HAContainer. However, we may still be receiving queue removal messages for that client which results in a decrement of those same HAEventWrappers. This double decrementing can result in premature removal of the HAEventWrapper from the HAContainer even though other clients still need it. We need to prevent this double decrementing and premature removal, perhaps through synchronization between the destroyRQ() logic and queue removal messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5495) Double decrement of HAEventWrapper ref count due to race between QRM and DestroyRQ
[ https://issues.apache.org/jira/browse/GEODE-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McMahon reassigned GEODE-5495: --- Assignee: Ryan McMahon > Double decrement of HAEventWrapper ref count due to race between QRM and > DestroyRQ > -- > > Key: GEODE-5495 > URL: https://issues.apache.org/jira/browse/GEODE-5495 > Project: Geode > Issue Type: Bug > Components: client queues >Reporter: Ryan McMahon >Assignee: Ryan McMahon >Priority: Major > Fix For: 1.8.0 > > > When a client disconnects due to network issues e.g. SocketTimeoutExceptions > we will destroy the HARegionQueue for that client. As part of that process, > we decrement the reference count on the HAEventWrappers used by that client > in the HAContainer. > However, we may still be receiving queue removal messages for that client > which results in a decrement of those same HAEventWrappers. This double > decrementing can result in premature removal of the HAEventWrapper from the > HAContainer even though other clients still need it. > We need to prevent this double decrementing and premature removal, perhaps > through synchronization between the destroyRQ() logic and queue removal > messages. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5437) Recovery of async persistent regions may result in inconsistency
[ https://issues.apache.org/jira/browse/GEODE-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562250#comment-16562250 ] ASF subversion and git services commented on GEODE-5437: Commit aaf030d81b14e5fbcbc661a262ae0d63240af1ba in geode's branch refs/heads/develop from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=aaf030d ] GEODE-5437: change async region gii to be synchronous (#2219) When a region uses async disk persistence it used to write its data to disk async but some of the gii meta-data synchronously. This could cause data inconsistency during recovery because it looked like the disk had the entire gii, when it may not have been able to write all the data. To fix this we now write all data to the disk store during gii synchronously for regions that are persistent even if they are configured async. DUnit tests have been added for both backup/restore and killing during gii. Unit tests have been added to cover the product changes. Also added bounceForcibly to the test framework which enables bounce to do a mean vm kill unlike bounce which always does a nice vm kill. > Recovery of async persistent regions may result in inconsistency > > > Key: GEODE-5437 > URL: https://issues.apache.org/jira/browse/GEODE-5437 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Kirk Lund >Assignee: Anilkumar Gingade >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > The region initialized flag is written to IF file synchronously, but the data > is written to CRF asynchronously, then servers may become inconsistent during > recovery. > Proposed fix: > Async region should perform disk store flush BEFORE writing region > initialized flag to the IF file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5451) SUPERFLAKY: LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure fails intermittently
[ https://issues.apache.org/jira/browse/GEODE-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-5451: --- Summary: SUPERFLAKY: LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure fails intermittently (was: LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure fails intermittently) > SUPERFLAKY: LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure > fails intermittently > -- > > Key: GEODE-5451 > URL: https://issues.apache.org/jira/browse/GEODE-5451 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Jens Deppe >Priority: Major > Labels: swat > Attachments: Test results - Class > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.html > > > Saw the following failure in a precheckin run: > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$109/561146633.run > in VM -2 running on Host e3827a7d1083 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219){noformat} > Test results can be found here: > http://files.apachegeode-ci.info/builds/geode-pr-2153/test-results/disitributedTest/1531949620/ > http://files.apachegeode-ci.info/builds/geode-pr-2153/test-artifacts/1531949620/distributedtesteverythingelse-geode-pr-2153.tgz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5437) Recovery of async persistent regions may result in inconsistency
[ https://issues.apache.org/jira/browse/GEODE-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider resolved GEODE-5437. - Resolution: Fixed Fix Version/s: 1.7.0 > Recovery of async persistent regions may result in inconsistency > > > Key: GEODE-5437 > URL: https://issues.apache.org/jira/browse/GEODE-5437 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Kirk Lund >Assignee: Anilkumar Gingade >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The region initialized flag is written to IF file synchronously, but the data > is written to CRF asynchronously, then servers may become inconsistent during > recovery. > Proposed fix: > Async region should perform disk store flush BEFORE writing region > initialized flag to the IF file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5482) Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure
[ https://issues.apache.org/jira/browse/GEODE-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-5482. Resolution: Duplicate > Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure > -- > > Key: GEODE-5482 > URL: https://issues.apache.org/jira/browse/GEODE-5482 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: flaky, swat > > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$112/1065764231.run > in VM -2 running on Host d0a2838cf5a3 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219) > {noformat} > See failed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/156#L5b4cf8d7:1404 > See passed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/155#L5b59f1be:1388 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5482) Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure
[ https://issues.apache.org/jira/browse/GEODE-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-5482. Resolution: Fixed > Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure > -- > > Key: GEODE-5482 > URL: https://issues.apache.org/jira/browse/GEODE-5482 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: flaky, swat > > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$112/1065764231.run > in VM -2 running on Host d0a2838cf5a3 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219) > {noformat} > See failed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/156#L5b4cf8d7:1404 > See passed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/155#L5b59f1be:1388 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GEODE-5482) Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure
[ https://issues.apache.org/jira/browse/GEODE-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson reopened GEODE-5482: > Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure > -- > > Key: GEODE-5482 > URL: https://issues.apache.org/jira/browse/GEODE-5482 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: flaky, swat > > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$112/1065764231.run > in VM -2 running on Host d0a2838cf5a3 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219) > {noformat} > See failed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/156#L5b4cf8d7:1404 > See passed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/155#L5b59f1be:1388 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5451) SUPERFLAKY: LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure fails intermittently
[ https://issues.apache.org/jira/browse/GEODE-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Rowe reassigned GEODE-5451: - Assignee: Brian Rowe > SUPERFLAKY: LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure > fails intermittently > -- > > Key: GEODE-5451 > URL: https://issues.apache.org/jira/browse/GEODE-5451 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Jens Deppe >Assignee: Brian Rowe >Priority: Major > Labels: swat > Attachments: Test results - Class > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.html > > > Saw the following failure in a precheckin run: > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$109/561146633.run > in VM -2 running on Host e3827a7d1083 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219){noformat} > Test results can be found here: > http://files.apachegeode-ci.info/builds/geode-pr-2153/test-results/disitributedTest/1531949620/ > http://files.apachegeode-ci.info/builds/geode-pr-2153/test-artifacts/1531949620/distributedtesteverythingelse-geode-pr-2153.tgz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-2022) CI Failure: PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
[ https://issues.apache.org/jira/browse/GEODE-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson resolved GEODE-2022. Resolution: Duplicate > CI Failure: PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes > -- > > Key: GEODE-2022 > URL: https://issues.apache.org/jira/browse/GEODE-2022 > Project: Geode > Issue Type: Bug > Components: querying >Reporter: Dan Smith >Priority: Major > Labels: CI, flaky > > This test failed in a precheckin run with revision > e130e5b62bcb2d3c561be90f46407dc49f100b4a > {noformat} > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache.query.partitioned.PRQueryDUnitHelper$33.run in VM 0 > running on Host f83af001cb71 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:389) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at org.apache.geode.test.dunit.VM.invoke(VM.java:293) > at > org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes(PRColocatedEquiJoinDUnitTest.java:1419) > 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 > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:114) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:57) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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 > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) > 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:4
[jira] [Commented] (GEODE-5440) Flaky PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
[ https://issues.apache.org/jira/browse/GEODE-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562281#comment-16562281 ] Mark Hanson commented on GEODE-5440: This failed in a more recent build {noformat} org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.cache.query.partitioned.PRQueryDUnitHelper$36.run in VM 0 running on Host 19ff35993c70 with 4 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:443) at org.apache.geode.test.dunit.VM.invoke(VM.java:412) at org.apache.geode.test.dunit.VM.invoke(VM.java:355) at org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes(PRColocatedEquiJoinDUnitTest.java:873) 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) 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 org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy1.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) 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 org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:155) at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConnection.java:137) at org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:404) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadP
[jira] [Updated] (GEODE-5482) Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure
[ https://issues.apache.org/jira/browse/GEODE-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-5482: --- Attachment: Test results - Class org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.html > Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure > -- > > Key: GEODE-5482 > URL: https://issues.apache.org/jira/browse/GEODE-5482 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: flaky, swat > Attachments: Test results - Class > org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.html > > > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$112/1065764231.run > in VM -2 running on Host d0a2838cf5a3 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219) > {noformat} > See failed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/156#L5b4cf8d7:1404 > See passed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/155#L5b59f1be:1388 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5482) Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure
[ https://issues.apache.org/jira/browse/GEODE-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-5482: --- Attachment: (was: Test results - Class org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.html) > Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure > -- > > Key: GEODE-5482 > URL: https://issues.apache.org/jira/browse/GEODE-5482 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: flaky, swat > > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$112/1065764231.run > in VM -2 running on Host d0a2838cf5a3 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219) > {noformat} > See failed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/156#L5b4cf8d7:1404 > See passed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/155#L5b59f1be:1388 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5440) SUPERFLAKY PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
[ https://issues.apache.org/jira/browse/GEODE-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-5440: --- Summary: SUPERFLAKY PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes (was: Flaky PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes) > SUPERFLAKY PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes > - > > Key: GEODE-5440 > URL: https://issues.apache.org/jira/browse/GEODE-5440 > Project: Geode > Issue Type: Bug > Components: querying >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: swat > Attachments: Test results - Class > org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.html > > > Flaky test in CI distributedTest job. > {noformat} > > Task :geode-core:distributedTest > org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest > > testRRPRLocalQueryingWithHetroIndexes FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache.query.partitioned.PRQueryDUnitHelper$36.run in VM 0 > running on Host 2709b168a57a with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes(PRColocatedEquiJoinDUnitTest.java:873) > Caused by: > java.lang.AssertionError: FAILED:SelectResults size is different in > both the cases. Size1=292 Size2 = 400; failed query=r1.ID = r2.id > {noformat} > Artifacts at > http://files.apachegeode-ci.info/builds/geode-pr-2126/test-artifacts/1531783070/distributedtestcore-geode-pr-2126.tgz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5440) Flaky PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes
[ https://issues.apache.org/jira/browse/GEODE-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-5440: --- Attachment: Test results - Class org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.html > Flaky PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes > > > Key: GEODE-5440 > URL: https://issues.apache.org/jira/browse/GEODE-5440 > Project: Geode > Issue Type: Bug > Components: querying >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: swat > Attachments: Test results - Class > org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.html > > > Flaky test in CI distributedTest job. > {noformat} > > Task :geode-core:distributedTest > org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest > > testRRPRLocalQueryingWithHetroIndexes FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache.query.partitioned.PRQueryDUnitHelper$36.run in VM 0 > running on Host 2709b168a57a with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.cache.query.partitioned.PRColocatedEquiJoinDUnitTest.testRRPRLocalQueryingWithHetroIndexes(PRColocatedEquiJoinDUnitTest.java:873) > Caused by: > java.lang.AssertionError: FAILED:SelectResults size is different in > both the cases. Size1=292 Size2 = 400; failed query=r1.ID = r2.id > {noformat} > Artifacts at > http://files.apachegeode-ci.info/builds/geode-pr-2126/test-artifacts/1531783070/distributedtestcore-geode-pr-2126.tgz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-632) CI failure: DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult
[ https://issues.apache.org/jira/browse/GEODE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Hanson updated GEODE-632: -- Labels: CI Flaky swat (was: CI Flaky) > CI failure: > DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult > - > > Key: GEODE-632 > URL: https://issues.apache.org/jira/browse/GEODE-632 > Project: Geode > Issue Type: Bug > Components: functions >Reporter: Darrel Schneider >Priority: Major > Labels: CI, Flaky, swat > > git rev 9283282c64076c5f8e599f3d47895f3c48e205e8 build #813 > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 4649 > [fatal 2015/12/06 15:02:06.760 PST > tid=0x233b] Uncaught exception processing > com.gemstone.gemfire.internal.cache.FunctionStreamingReplyMessage(processorId=10999 > from cc4-rh6(25294):1027;msgNum 0;lastMsg=false) > com.gemstone.gemfire.cache.execute.FunctionException: IOException while > sending the result chunk to client > at > com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:247) > at > com.gemstone.gemfire.internal.cache.execute.DistributedRegionFunctionResultSender.sendResult(DistributedRegionFunctionResultSender.java:204) > at > com.gemstone.gemfire.internal.cache.execute.StreamingFunctionOperation.processData(StreamingFunctionOperation.java:93) > at > com.gemstone.gemfire.internal.cache.execute.FunctionStreamingResultCollector.process(FunctionStreamingResultCollector.java:541) > at > com.gemstone.gemfire.distributed.internal.ReplyMessage.process(ReplyMessage.java:231) > at > com.gemstone.gemfire.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:212) > at > com.gemstone.gemfire.distributed.internal.ReplyMessage.process(ReplyMessage.java:201) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:380) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:451) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at > com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:658) > at > com.gemstone.gemfire.distributed.internal.DistributionManager$5$1.run(DistributionManager.java:969) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketException: Socket closed > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116) > at java.net.SocketOutputStream.write(SocketOutputStream.java:153) > at > com.gemstone.gemfire.internal.cache.tier.sockets.Message.flushBuffer(Message.java:668) > at > com.gemstone.gemfire.internal.cache.tier.sockets.ChunkedMessage.sendHeader(ChunkedMessage.java:295) > at > com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender.sendHeader(ServerToClientFunctionResultSender.java:271) > at > com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:228) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-632) CI failure: DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult
[ https://issues.apache.org/jira/browse/GEODE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562290#comment-16562290 ] Mark Hanson commented on GEODE-632: --- This is failing 9/300 times {noformat} java.lang.AssertionError: Suspicious strings were written to the log during this run. Fix the strings or use IgnoredException.addIgnoredException to ignore. --- Found suspect string in log4j at line 2996 [fatal 2018/07/30 10:44:26.209 UTC tid=2430] Uncaught exception processing org.apache.geode.internal.cache.FunctionStreamingReplyMessage(processorId=841 from 172.17.0.41(260):32771;msgNum 0;lastMsg=false) org.apache.geode.cache.execute.FunctionException: IOException while sending the result chunk to client at org.apache.geode.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:251) at org.apache.geode.internal.cache.execute.DistributedRegionFunctionResultSender.sendResult(DistributedRegionFunctionResultSender.java:182) at org.apache.geode.internal.cache.execute.StreamingFunctionOperation.processData(StreamingFunctionOperation.java:84) at org.apache.geode.internal.cache.execute.FunctionStreamingResultCollector.process(FunctionStreamingResultCollector.java:499) at org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:209) at org.apache.geode.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:193) at org.apache.geode.distributed.internal.ReplyMessage.process(ReplyMessage.java:186) at org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:378) at org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:444) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:1146) at org.apache.geode.distributed.internal.ClusterDistributionManager.access$000(ClusterDistributionManager.java:113) at org.apache.geode.distributed.internal.ClusterDistributionManager$5$1.run(ClusterDistributionManager.java:857) at java.lang.Thread.run(Thread.java:748) Caused by: java.net.SocketException: Socket closed at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:118) at java.net.SocketOutputStream.write(SocketOutputStream.java:155) at org.apache.geode.internal.cache.tier.sockets.Message.flushBuffer(Message.java:644) at org.apache.geode.internal.cache.tier.sockets.ChunkedMessage.sendHeader(ChunkedMessage.java:286) at org.apache.geode.internal.cache.execute.ServerToClientFunctionResultSender.sendHeader(ServerToClientFunctionResultSender.java:286) at org.apache.geode.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:233) ... 14 more at org.junit.Assert.fail(Assert.java:88) at org.apache.geode.test.dunit.standalone.DUnitLauncher.closeAndCheckForSuspects(DUnitLauncher.java:411) at org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.cleanupAllVms(JUnit4DistributedTestCase.java:562) at org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.doTearDownDistributedTestCase(JUnit4DistributedTestCase.java:509) at org.apache.geode.test.dunit.internal.JUnit4DistributedTestCase.tearDownDistributedTestCase(JUnit4DistributedTestCase.java:496) at sun.reflect.GeneratedMethodAccessor345.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) 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) a
[jira] [Commented] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed
[ https://issues.apache.org/jira/browse/GEODE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562317#comment-16562317 ] ASF subversion and git services commented on GEODE-5400: Commit 1b5b8ebe3b4a20475a62293a68c89569134d8fca in geode's branch refs/heads/feature/GEODE-5400 from eshu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1b5b8eb ] GEODE-5400: Cleanup locks if held during TXState.close. > JTA transaction locks are not released if the jta originator is crashed after > beforeCompletion is executed > -- > > Key: GEODE-5400 > URL: https://issues.apache.org/jira/browse/GEODE-5400 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > Currently when the JTA originator is departed, a membership listener will be > invoked to clean the transactions initiated by the departed member. However, > if the member is departed after JTA beforeCompletion is run, the locks are > not released. > Here is a distributed test failure showing new transaction could not finish > even though the JTA transaction was closed/removed after the memberDeparted > invocation. > {noformat} > rg.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.tx.ClientServerJTAFailoverDistributedTest$$Lambda$26/573958827.run > in VM 0 running on Host 10.118.20.64 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.tx.ClientServerJTAFailoverDistributedTest.locksHeldInBeforeCompletionCanBeReleaseIfOriginatorDeparted(ClientServerJTAFailoverDistributedTest.java:284) > 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 > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > 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.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: org.apache.geode.cache.CommitConflictException: The key 1 in > region > /__PR/_B__ClientServerJTAFailoverDistributedTest__locksHeldInBeforeCompletionCanBeReleaseIfOriginatorDeparted__region_0 > was being modified by another transaction locally. > at > org.apache.geode.internal.cache.TXReservationMgr.checkSetForConflict(TXReservationMgr.java:107) > at > org.apache.geode.internal.cache.TXReservationMgr.ch
[jira] [Updated] (GEODE-5470) SUPERFLAKY: DlockAndTxlockRegressionTest > testDLockProtectsAgainstTransactionConflict FAILED
[ https://issues.apache.org/jira/browse/GEODE-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5470: - Summary: SUPERFLAKY: DlockAndTxlockRegressionTest > testDLockProtectsAgainstTransactionConflict FAILED (was: DlockAndTxlockRegressionTest > testDLockProtectsAgainstTransactionConflict FAILED) > SUPERFLAKY: DlockAndTxlockRegressionTest > > testDLockProtectsAgainstTransactionConflict FAILED > - > > Key: GEODE-5470 > URL: https://issues.apache.org/jira/browse/GEODE-5470 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Priority: Major > Labels: swat > > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139 > > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest > > testDLockProtectsAgainstTransactionConflict FAILED > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:255] > java.lang.RuntimeException: test failed > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:256] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.testDLockProtectsAgainstTransactionConflict(DlockAndTxlockRegressionTest.java:161) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:257] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:258] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:259] > java.lang.RuntimeException: dlock failed to prevent a transaction conflict > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:260] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.performOps(DlockAndTxlockRegressionTest.java:234) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:261] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.lambda$testDLockProtectsAgainstTransactionConflict$bb17a952$5(DlockAndTxlockRegressionTest.java:123) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:262] > > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:263] > Caused by: > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:264] > org.apache.geode.cache.CommitConflictException: Concurrent transaction > commit detected The key TestKey in region /TestRegion was being modified by > another transaction locally. > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:265] > at > org.apache.geode.internal.cache.locks.TXLockServiceImpl.txLock(TXLockServiceImpl.java:137) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:266] > at > org.apache.geode.internal.cache.TXLockRequest.obtain(TXLockRequest.java:88) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:267] > at org.apache.geode.internal.cache.TXState.reserveAndCheck(TXState.java:340) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:268] > at org.apache.geode.internal.cache.TXState.commit(TXState.java:411) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:269] > at > org.apache.geode.internal.cache.TXStateProxyImpl.commit(TXStateProxyImpl.java:210) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:270] > at > org.apache.geode.internal.cache.TXManagerImpl.commit(TXManagerImpl.java:413) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:271] > at > org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.performOps(DlockAndTxlockRegressionTest.java:232) > [ > |https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/139#L5b4cf155:272] > ... 1 more > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-632) SUPERFLAKY: DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult
[ https://issues.apache.org/jira/browse/GEODE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-632: Summary: SUPERFLAKY: DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult (was: CI failure: DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult) > SUPERFLAKY: > DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult > - > > Key: GEODE-632 > URL: https://issues.apache.org/jira/browse/GEODE-632 > Project: Geode > Issue Type: Bug > Components: functions >Reporter: Darrel Schneider >Priority: Major > Labels: CI, Flaky, swat > > git rev 9283282c64076c5f8e599f3d47895f3c48e205e8 build #813 > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use DistributedTestCase.addExpectedException to ignore. > --- > Found suspect string in log4j at line 4649 > [fatal 2015/12/06 15:02:06.760 PST > tid=0x233b] Uncaught exception processing > com.gemstone.gemfire.internal.cache.FunctionStreamingReplyMessage(processorId=10999 > from cc4-rh6(25294):1027;msgNum 0;lastMsg=false) > com.gemstone.gemfire.cache.execute.FunctionException: IOException while > sending the result chunk to client > at > com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:247) > at > com.gemstone.gemfire.internal.cache.execute.DistributedRegionFunctionResultSender.sendResult(DistributedRegionFunctionResultSender.java:204) > at > com.gemstone.gemfire.internal.cache.execute.StreamingFunctionOperation.processData(StreamingFunctionOperation.java:93) > at > com.gemstone.gemfire.internal.cache.execute.FunctionStreamingResultCollector.process(FunctionStreamingResultCollector.java:541) > at > com.gemstone.gemfire.distributed.internal.ReplyMessage.process(ReplyMessage.java:231) > at > com.gemstone.gemfire.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:212) > at > com.gemstone.gemfire.distributed.internal.ReplyMessage.process(ReplyMessage.java:201) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:380) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:451) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at > com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:658) > at > com.gemstone.gemfire.distributed.internal.DistributionManager$5$1.run(DistributionManager.java:969) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.net.SocketException: Socket closed > at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116) > at java.net.SocketOutputStream.write(SocketOutputStream.java:153) > at > com.gemstone.gemfire.internal.cache.tier.sockets.Message.flushBuffer(Message.java:668) > at > com.gemstone.gemfire.internal.cache.tier.sockets.ChunkedMessage.sendHeader(ChunkedMessage.java:295) > at > com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender.sendHeader(ServerToClientFunctionResultSender.java:271) > at > com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:228) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5480) SUPERFLAKY test UniversalMembershipListenerAdapterDUnitTest > testSystemClientEventsInServer
[ https://issues.apache.org/jira/browse/GEODE-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5480: - Summary: SUPERFLAKY test UniversalMembershipListenerAdapterDUnitTest > testSystemClientEventsInServer (was: Flaky test UniversalMembershipListenerAdapterDUnitTest > testSystemClientEventsInServer) > SUPERFLAKY test UniversalMembershipListenerAdapterDUnitTest > > testSystemClientEventsInServer > > > Key: GEODE-5480 > URL: https://issues.apache.org/jira/browse/GEODE-5480 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: flaky, swat > Attachments: Test results - Class > org.apache.geode.management.UniversalMembershipListenerAdapterDUnitTest.html > > > {noformat} > org.apache.geode.management.UniversalMembershipListenerAdapterDUnitTest > > testSystemClientEventsInServer FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.UniversalMembershipListenerAdapterDUnitTest.testSystemClientEventsInServer(UniversalMembershipListenerAdapterDUnitTest.java:699) > {noformat} > See failure: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/151#L5b4cf768:7281 > See pass: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/152#L5b59cf6d:7039 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5437) Recovery of async persistent regions may result in inconsistency
[ https://issues.apache.org/jira/browse/GEODE-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562342#comment-16562342 ] ASF subversion and git services commented on GEODE-5437: Commit aaf030d81b14e5fbcbc661a262ae0d63240af1ba in geode's branch refs/heads/feature/GEODE-5400 from agingade [ https://gitbox.apache.org/repos/asf?p=geode.git;h=aaf030d ] GEODE-5437: change async region gii to be synchronous (#2219) When a region uses async disk persistence it used to write its data to disk async but some of the gii meta-data synchronously. This could cause data inconsistency during recovery because it looked like the disk had the entire gii, when it may not have been able to write all the data. To fix this we now write all data to the disk store during gii synchronously for regions that are persistent even if they are configured async. DUnit tests have been added for both backup/restore and killing during gii. Unit tests have been added to cover the product changes. Also added bounceForcibly to the test framework which enables bounce to do a mean vm kill unlike bounce which always does a nice vm kill. > Recovery of async persistent regions may result in inconsistency > > > Key: GEODE-5437 > URL: https://issues.apache.org/jira/browse/GEODE-5437 > Project: Geode > Issue Type: Bug > Components: persistence >Reporter: Kirk Lund >Assignee: Anilkumar Gingade >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The region initialized flag is written to IF file synchronously, but the data > is written to CRF asynchronously, then servers may become inconsistent during > recovery. > Proposed fix: > Async region should perform disk store flush BEFORE writing region > initialized flag to the IF file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5411) SUPERFLAKY: CI Failure CqPerfDUnitTest.testFailOverMatchingCQsWithMultipleServers
[ https://issues.apache.org/jira/browse/GEODE-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5411: - Summary: SUPERFLAKY: CI Failure CqPerfDUnitTest.testFailOverMatchingCQsWithMultipleServers (was: CI Failure CqPerfDUnitTest.testFailOverMatchingCQsWithMultipleServers) > SUPERFLAKY: CI Failure > CqPerfDUnitTest.testFailOverMatchingCQsWithMultipleServers > - > > Key: GEODE-5411 > URL: https://issues.apache.org/jira/browse/GEODE-5411 > Project: Geode > Issue Type: Task > Components: cq >Reporter: Dan Smith >Priority: Major > Labels: swat > > This test failed in CI on revision b79b64a7cbdc4de1ffc1fe34222b56ac867ab38c > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/104 > I see there is a closed Jira for this same method name in a different test - > see GEODE-4172. The method appears to have been copied and pasted, so maybe > the fix didn't make it to this copy? We should fix this test and ideally > remove the duplicate code as well! > {noformat} > org.apache.geode.cache.query.cq.dunit.CqPerfDUnitTest > > testFailOverMatchingCQsWithMultipleServers FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.cache.query.cq.dunit.CqPerfDUnitTest$10.run in VM 1 running > on Host 7872e0cd247b 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.cache.query.cq.dunit.CqPerfDUnitTest.validateMatchingCqs(CqPerfDUnitTest.java:958) > at > org.apache.geode.cache.query.cq.dunit.CqPerfDUnitTest.testFailOverMatchingCQsWithMultipleServers(CqPerfDUnitTest.java:804) > Caused by: > java.lang.AssertionError: Number of matched cqs are not equal to the > expected matched cqs expected:<2> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:645) > at > org.apache.geode.cache.query.cq.dunit.CqPerfDUnitTest$10.run2(CqPerfDUnitTest.java:977) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5488) Use docker gradle plugin to execute all tests in parallel
[ https://issues.apache.org/jira/browse/GEODE-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562333#comment-16562333 ] ASF subversion and git services commented on GEODE-5488: Commit 990234297c2b5f0cfccfdfef8387cb8bf8e85a0d in geode's branch refs/heads/feature/GEODE-5400 from [~rhoughton] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=9902342 ] GEODE-5488 - Enable docker for all of our gradle tests (#2215) Integration, Performance, UI, Upgrade, Distributed tests will all use the dockerized-gradle-plugin as the test executor when enabled via gradle property. Co-authored-by: Dick Cavender Co-authored-by: Patrick Rhomberg Co-authored-by: Robert Houghton > Use docker gradle plugin to execute all tests in parallel > - > > Key: GEODE-5488 > URL: https://issues.apache.org/jira/browse/GEODE-5488 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Adding more test target types to run with Docker. Allows better environment > isolation and parallelism. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5464) Add generics to DistributionManager
[ https://issues.apache.org/jira/browse/GEODE-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562339#comment-16562339 ] ASF subversion and git services commented on GEODE-5464: Commit 58715ac2f0bb086c577d204131c129a4338b07c9 in geode's branch refs/heads/feature/GEODE-5400 from [~gosullivan] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=58715ac ] GEODE-5464: Generify DistributionManager and related classes (#2174) GEODE-5464: Generify DistributionManager and related classes * Augment various collections to use generics * Inline some iterator loops that were trivially "foreach" loops * remove unused code * Inline some redundant local variables * make some methods more private * change some tests to use `InternalDistributedMember` instead of `DistributedMember`. * Make ThrottlingMemLinkedQueueWithDMStats generic and use atomic. - The previous synchronization looked quite wrong. > Add generics to DistributionManager > --- > > Key: GEODE-5464 > URL: https://issues.apache.org/jira/browse/GEODE-5464 > Project: Geode > Issue Type: Bug > Components: membership, messaging >Reporter: Galen O'Sullivan >Assignee: Galen O'Sullivan >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > DistributionManager has a number of methods that take/return various > {{Collection}} types without specifying the types of the elements in the > collection. This code would be significantly more readable and understandable > if generics were added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5476) Change pipeline to run all tests in external instances for performance
[ https://issues.apache.org/jira/browse/GEODE-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562338#comment-16562338 ] ASF subversion and git services commented on GEODE-5476: Commit 3e8a9368f58256eb39b79881bf7abd9fe2f5f5f5 in geode's branch refs/heads/feature/GEODE-5400 from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=3e8a936 ] GEODE-5476: Reduce build output while preserving some sense of progress. (#) > Change pipeline to run all tests in external instances for performance > -- > > Key: GEODE-5476 > URL: https://issues.apache.org/jira/browse/GEODE-5476 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Sean Goller >Priority: Major > Labels: pull-request-available > Time Spent: 1h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5478) The lowRedundancyBucketCount statistic is not maintained properly when multiple members are stopped and restarted
[ https://issues.apache.org/jira/browse/GEODE-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562334#comment-16562334 ] ASF subversion and git services commented on GEODE-5478: Commit 12e17d80629bfd4193b3bcd603a75eb9694c8107 in geode's branch refs/heads/feature/GEODE-5400 from [~barry.oglesby] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=12e17d8 ] GEODE-5478: Modified to not increment low redundancy bucket count twice Co-authored-by: Darrel Schneider > The lowRedundancyBucketCount statistic is not maintained properly when > multiple members are stopped and restarted > - > > Key: GEODE-5478 > URL: https://issues.apache.org/jira/browse/GEODE-5478 > Project: Geode > Issue Type: Bug > Components: regions, statistics >Reporter: Barry Oglesby >Assignee: Barry Oglesby >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > The lowRedundancyBucketCount statistic is not maintained properly when > multiple members are stopped and restarted > A test where multiple members are stopped simultaneously so that all copies > of a bucket are offlineshows the numBucketsWithoutRedundancy metric not set > properly: > Initially: > {noformat} > (2) Executing - show metrics --categories=partition --region=/rewards > Category | Metric | Value > - | --- | -- > partition | putLocalRate | 0.0 > | putRemoteRate | 0.0 > | putRemoteLatency | 0 > | putRemoteAvgLatency | 0 > | bucketCount | 226 > | primaryBucketCount | 113 > | numBucketsWithoutRedundancy | 0 > | totalBucketSize | 20 > | averageBucketSize | 221 > (3) Executing - show metrics --categories=partition --region=/customer > Category | Metric | Value > - | --- | - > partition | putLocalRate | 0.0 > | putRemoteRate | 0.0 > | putRemoteLatency | 0 > | putRemoteAvgLatency | 0 > | bucketCount | 226 > | primaryBucketCount | 113 > | numBucketsWithoutRedundancy | 0 > | totalBucketSize | 2 > | averageBucketSize | 22 > {noformat} > After stopping 2 members (of 4): > {noformat} > (2) Executing - show metrics --categories=partition --region=/rewards > Category | Metric | Value > - | --- | - > partition | putLocalRate | 0.0 > | putRemoteRate | 0.0 > | putRemoteLatency | 0 > | putRemoteAvgLatency | 0 > | bucketCount | 112 > | primaryBucketCount | 73 > | numBucketsWithoutRedundancy | 57 > | totalBucketSize | 99107 > | averageBucketSize | 442 > (3) Executing - show metrics --categories=partition --region=/customer > Category | Metric | Value > - | --- | - > partition | putLocalRate | 0.0 > | putRemoteRate | 0.0 > | putRemoteLatency | 0 > | putRemoteAvgLatency | 0 > | bucketCount | 112 > | primaryBucketCount | 76 > | numBucketsWithoutRedundancy | 57 > | totalBucketSize | 9915 > | averageBucketSize | 44 > {noformat} > After restarting both members, numBucketsWithoutRedundancy > 0: > {noformat} > (2) Executing - show metrics --categories=partition --region=/rewards > Category | Metric | Value > - | --- | -- > partition | putLocalRate | 0.0 > | putRemoteRate | 0.0 > | putRemoteLatency | 0 > | putRemoteAvgLatency | 0 > | bucketCount | 226 > | primaryBucketCount | 113 > | numBucketsWithoutRedundancy | 0 > | totalBucketSize | 20 > | averageBucketSize | 221 > (3) Executing - show metrics --categories=partition --region=/customer > Category | Metric | Value > - | --- | - > partition | putLocalRate | 0.0 > | putRemoteRate | 0.0 > | putRemoteLatency | 0 > | putRemoteAvgLatency | 0 > | bucketCount | 226 > | primaryBucketCount | 113 > | numBucketsWithoutRedundancy | 21 > | totalBucketSize | 2 > | averageBucketSize | 22 > {noformat} > All the buckets and data are recovered, but the numBucketsWithoutRedundancy > is not 0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5443) Stop the UITests pipeline from automatically running.
[ https://issues.apache.org/jira/browse/GEODE-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562341#comment-16562341 ] ASF subversion and git services commented on GEODE-5443: Commit 82a5fe6342113cacfdcc3002015a8e6a18e02cf7 in geode's branch refs/heads/feature/GEODE-5400 from mhansonp [ https://gitbox.apache.org/repos/asf?p=geode.git;h=82a5fe6 ] GEODE-5443: removing uiTests from the CI > Stop the UITests pipeline from automatically running. > - > > Key: GEODE-5443 > URL: https://issues.apache.org/jira/browse/GEODE-5443 > Project: Geode > Issue Type: Task > Components: ci >Reporter: Mark Hanson >Assignee: Mark Hanson >Priority: Major > Labels: pull-request-available, swat > Time Spent: 2h 20m > Remaining Estimate: 0h > > The UI Tests are flaky, so we don't want to automatically run it anymore. We > want to manually run it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed
[ https://issues.apache.org/jira/browse/GEODE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562343#comment-16562343 ] ASF subversion and git services commented on GEODE-5400: Commit efcffbdaff9b72092f239792efff77df107010e9 in geode's branch refs/heads/feature/GEODE-5400 from eshu [ https://gitbox.apache.org/repos/asf?p=geode.git;h=efcffbd ] GEODE-5400: Cleanup locks if held during TXState.close. > JTA transaction locks are not released if the jta originator is crashed after > beforeCompletion is executed > -- > > Key: GEODE-5400 > URL: https://issues.apache.org/jira/browse/GEODE-5400 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > > Currently when the JTA originator is departed, a membership listener will be > invoked to clean the transactions initiated by the departed member. However, > if the member is departed after JTA beforeCompletion is run, the locks are > not released. > Here is a distributed test failure showing new transaction could not finish > even though the JTA transaction was closed/removed after the memberDeparted > invocation. > {noformat} > rg.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.tx.ClientServerJTAFailoverDistributedTest$$Lambda$26/573958827.run > in VM 0 running on Host 10.118.20.64 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.tx.ClientServerJTAFailoverDistributedTest.locksHeldInBeforeCompletionCanBeReleaseIfOriginatorDeparted(ClientServerJTAFailoverDistributedTest.java:284) > 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 > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > 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.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: org.apache.geode.cache.CommitConflictException: The key 1 in > region > /__PR/_B__ClientServerJTAFailoverDistributedTest__locksHeldInBeforeCompletionCanBeReleaseIfOriginatorDeparted__region_0 > was being modified by another transaction locally. > at > org.apache.geode.internal.cache.TXReservationMgr.checkSetForConflict(TXReservationMgr.java:107) > at > org.apache.geode.internal.cache.TXReservationMgr.ch
[jira] [Commented] (GEODE-5488) Use docker gradle plugin to execute all tests in parallel
[ https://issues.apache.org/jira/browse/GEODE-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562336#comment-16562336 ] ASF subversion and git services commented on GEODE-5488: Commit b1890b28dc9195fac1d5aa2f4b7acf52a0e669fb in geode's branch refs/heads/feature/GEODE-5400 from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b1890b2 ] GEODE-5488: Fixes bad merge that remove distributeTest. > Use docker gradle plugin to execute all tests in parallel > - > > Key: GEODE-5488 > URL: https://issues.apache.org/jira/browse/GEODE-5488 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Adding more test target types to run with Docker. Allows better environment > isolation and parallelism. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5489) createVersionPropertiesFile task should run only on changes to .git/index
[ https://issues.apache.org/jira/browse/GEODE-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562335#comment-16562335 ] ASF subversion and git services commented on GEODE-5489: Commit 4b7e789981568e3c38eced1438924be84df3ade2 in geode's branch refs/heads/feature/GEODE-5400 from FSOUTHERLAND [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4b7e789 ] GEODE-5489 Create version properties file less (#2213) Co-authored-by: Jacob Barrett Co-authored-by: Finn Southerland > createVersionPropertiesFile task should run only on changes to .git/index > - > > Key: GEODE-5489 > URL: https://issues.apache.org/jira/browse/GEODE-5489 > Project: Geode > Issue Type: Improvement >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Updating this file too often triggers other tasks unnecessarily. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5494) Flaky test DiskSpaceLimitIntegrationTest > aboveZeroDeletesPreviousFiles
[ https://issues.apache.org/jira/browse/GEODE-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562337#comment-16562337 ] ASF subversion and git services commented on GEODE-5494: Commit 0c9b0d507c2ab968e50cebc48700faf8114a8efb in geode's branch refs/heads/feature/GEODE-5400 from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0c9b0d5 ] GEODE-5494: Ignore until dockerization issues resolved. > Flaky test DiskSpaceLimitIntegrationTest > aboveZeroDeletesPreviousFiles > > > Key: GEODE-5494 > URL: https://issues.apache.org/jira/browse/GEODE-5494 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Jacob S. Barrett >Priority: Major > > This test fails frequently in docker container but passes outside. It is the > only integration test that is failing as a result of dockerization. I am > going to mark it {{@Ignore}} until this ticket fixes it. > {noformat} > org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest > > aboveZeroDeletesPreviousFiles FAILED > java.lang.AssertionError: > Expecting file: > > to exist. > at > org.apache.geode.internal.statistics.DiskSpaceLimitIntegrationTest.aboveZeroDeletesPreviousFiles(DiskSpaceLimitIntegrationTest.java:205) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5464) Add generics to DistributionManager
[ https://issues.apache.org/jira/browse/GEODE-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562340#comment-16562340 ] ASF subversion and git services commented on GEODE-5464: Commit 58715ac2f0bb086c577d204131c129a4338b07c9 in geode's branch refs/heads/feature/GEODE-5400 from [~gosullivan] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=58715ac ] GEODE-5464: Generify DistributionManager and related classes (#2174) GEODE-5464: Generify DistributionManager and related classes * Augment various collections to use generics * Inline some iterator loops that were trivially "foreach" loops * remove unused code * Inline some redundant local variables * make some methods more private * change some tests to use `InternalDistributedMember` instead of `DistributedMember`. * Make ThrottlingMemLinkedQueueWithDMStats generic and use atomic. - The previous synchronization looked quite wrong. > Add generics to DistributionManager > --- > > Key: GEODE-5464 > URL: https://issues.apache.org/jira/browse/GEODE-5464 > Project: Geode > Issue Type: Bug > Components: membership, messaging >Reporter: Galen O'Sullivan >Assignee: Galen O'Sullivan >Priority: Major > Labels: pull-request-available > Time Spent: 1.5h > Remaining Estimate: 0h > > DistributionManager has a number of methods that take/return various > {{Collection}} types without specifying the types of the elements in the > collection. This code would be significantly more readable and understandable > if generics were added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5400) JTA transaction locks are not released if the jta originator is crashed after beforeCompletion is executed
[ https://issues.apache.org/jira/browse/GEODE-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5400: -- Labels: pull-request-available (was: ) > JTA transaction locks are not released if the jta originator is crashed after > beforeCompletion is executed > -- > > Key: GEODE-5400 > URL: https://issues.apache.org/jira/browse/GEODE-5400 > Project: Geode > Issue Type: Bug > Components: transactions >Reporter: Eric Shu >Assignee: Eric Shu >Priority: Major > Labels: pull-request-available > > Currently when the JTA originator is departed, a membership listener will be > invoked to clean the transactions initiated by the departed member. However, > if the member is departed after JTA beforeCompletion is run, the locks are > not released. > Here is a distributed test failure showing new transaction could not finish > even though the JTA transaction was closed/removed after the memberDeparted > invocation. > {noformat} > rg.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.tx.ClientServerJTAFailoverDistributedTest$$Lambda$26/573958827.run > in VM 0 running on Host 10.118.20.64 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.tx.ClientServerJTAFailoverDistributedTest.locksHeldInBeforeCompletionCanBeReleaseIfOriginatorDeparted(ClientServerJTAFailoverDistributedTest.java:284) > 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 > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at > org.apache.geode.test.dunit.rules.AbstractDistributedTestRule$1.evaluate(AbstractDistributedTestRule.java:60) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > 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.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runner.JUnitCore.run(JUnitCore.java:137) > at > com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68) > at > com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47) > at > com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242) > at > com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70) > Caused by: org.apache.geode.cache.CommitConflictException: The key 1 in > region > /__PR/_B__ClientServerJTAFailoverDistributedTest__locksHeldInBeforeCompletionCanBeReleaseIfOriginatorDeparted__region_0 > was being modified by another transaction locally. > at > org.apache.geode.internal.cache.TXReservationMgr.checkSetForConflict(TXReservationMgr.java:107) > at > org.apache.geode.internal.cache.TXReservationMgr.checkForConflict(TXReservationMgr.java:77) > at > org.apache.geode.internal.cache.TXReservationMgr.makeReservation(TXReservationMgr.java:56) > at > org.apache.geode.internal.cache.TXLockRequest.txLocalLock(TXLockReque
[jira] [Created] (GEODE-5496) Create a reaper pipeline
Finn Southerland created GEODE-5496: --- Summary: Create a reaper pipeline Key: GEODE-5496 URL: https://issues.apache.org/jira/browse/GEODE-5496 Project: Geode Issue Type: Task Reporter: Finn Southerland We should shut down pipeline-created instances after a certain period if they do not get shut down for some reason. An additional concourse pipeline can do this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5496) Create a reaper pipeline
[ https://issues.apache.org/jira/browse/GEODE-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5496: -- Labels: pull-request-available (was: ) > Create a reaper pipeline > > > Key: GEODE-5496 > URL: https://issues.apache.org/jira/browse/GEODE-5496 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > > We should shut down pipeline-created instances after a certain period if they > do not get shut down for some reason. An additional concourse pipeline can do > this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5492) Fix parallel builds in Gradle
[ https://issues.apache.org/jira/browse/GEODE-5492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562463#comment-16562463 ] ASF subversion and git services commented on GEODE-5492: Commit e505ec8fc43f4d63ba5d0206a01095254410eec3 in geode's branch refs/heads/develop from [~rhoughton] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=e505ec8 ] GEODE-5492 Fix gradle dependencies to enable reliable parallel build (#2217) - distZip and distTar tasks wait for all 'jar' tasks to finish - geode-assembly:docs depends on all project's javadoc task - geode-core 'jar' depends on the version properties file - version properties file runs after compileJava - geode-pulse 'war' depends on the webJar, instead of only including it - fixed download of geode-old-versions to run after clean, even when specified backwards on the command line - srcJar no longer includes the IntelliJ output directory Co-authored-by: Patrick Rhomberg Co-authored-by: Finn Southerland Co-authored-by: Dick Cavender > Fix parallel builds in Gradle > - > > Key: GEODE-5492 > URL: https://issues.apache.org/jira/browse/GEODE-5492 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Robert Houghton >Priority: Major > Labels: pull-request-available > Fix For: 1.8.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Invoking `gradle build --parallel` twice is executing new tasks. This > indicates that some task dependencies are not correctly declared. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5496) Create a reaper pipeline
[ https://issues.apache.org/jira/browse/GEODE-5496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562469#comment-16562469 ] ASF subversion and git services commented on GEODE-5496: Commit 153fda255ff839a94a94ac7a91109f431638ad39 in geode's branch refs/heads/develop from FSOUTHERLAND [ https://gitbox.apache.org/repos/asf?p=geode.git;h=153fda2 ] GEODE-5496 create reaper pipeline (#2224) concourse instances now have ttl and are stopped and eventually deleted by a reaper pipline Co-authored-by: Jacob Barrett > Create a reaper pipeline > > > Key: GEODE-5496 > URL: https://issues.apache.org/jira/browse/GEODE-5496 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > Time Spent: 40m > Remaining Estimate: 0h > > We should shut down pipeline-created instances after a certain period if they > do not get shut down for some reason. An additional concourse pipeline can do > this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5497) BackupIntegrationTest should be testing incremental backups
Jens Deppe created GEODE-5497: - Summary: BackupIntegrationTest should be testing incremental backups Key: GEODE-5497 URL: https://issues.apache.org/jira/browse/GEODE-5497 Project: Geode Issue Type: Test Components: regions Reporter: Jens Deppe Add a test which validates the generated {{restore,sh}} script for incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5497) BackupIntegrationTest should be testing incremental backups
[ https://issues.apache.org/jira/browse/GEODE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-5497: - Assignee: Jens Deppe > BackupIntegrationTest should be testing incremental backups > --- > > Key: GEODE-5497 > URL: https://issues.apache.org/jira/browse/GEODE-5497 > Project: Geode > Issue Type: Test > Components: regions >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > > Add a test which validates the generated {{restore,sh}} script for > incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5497) BackupIntegrationTest should be testing incremental backups
[ https://issues.apache.org/jira/browse/GEODE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5497: -- Labels: pull-request-available (was: ) > BackupIntegrationTest should be testing incremental backups > --- > > Key: GEODE-5497 > URL: https://issues.apache.org/jira/browse/GEODE-5497 > Project: Geode > Issue Type: Test > Components: regions >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > > Add a test which validates the generated {{restore,sh}} script for > incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5490) Move backwards compatibility tests to updateTest source set and split up
[ https://issues.apache.org/jira/browse/GEODE-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562515#comment-16562515 ] ASF subversion and git services commented on GEODE-5490: Commit ee29dc62d15f6cdba452026dc41a3b71e02e2b97 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ee29dc6 ] GEODE-5490: Moves backwards compatibility tests in to upgradeTest. (#2221) * Split up TomcatSessionBackwardsCompatibilityTest * Split up TxCommitMessageBackwardsCompatibilityDUnitTest > Move backwards compatibility tests to updateTest source set and split up > > > Key: GEODE-5490 > URL: https://issues.apache.org/jira/browse/GEODE-5490 > Project: Geode > Issue Type: Improvement >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Improve distributed test runs by moving and splitting up backwards > compatibility tests. Make each test its own test class to improve parallel > execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5498) JMXMBeanReconnectDUnitTest disconnect and reconnect of members fails
Helena Bales created GEODE-5498: --- Summary: JMXMBeanReconnectDUnitTest disconnect and reconnect of members fails Key: GEODE-5498 URL: https://issues.apache.org/jira/browse/GEODE-5498 Project: Geode Issue Type: Bug Reporter: Helena Bales JMXMBeanReconnectDUnitTest > testRemoteBeanKnowledge_MaintainServerAndCrashLocator {{java.lang.AssertionError: Actual and expected should have same size but actual size was: <19> while expected size was: <15> Actual was: <[GemFire:service=Region,name="/test-region-1",type=Distributed, GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed, GemFire:service=AccessControl,type=Distributed, GemFire:service=FileUploader,type=Distributed, GemFire:service=System,type=Distributed, GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-one, GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-one, GemFire:service=Locator,type=Member,member=locator-one, GemFire:type=Member,member=locator-one, GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-two, GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-two, GemFire:service=Locator,type=Member,member=locator-two, GemFire:type=Member,member=locator-two, GemFire:service=Region,name="/test-region-1",type=Member,member=server-2, GemFire:service=CacheServer,port=43093,type=Member,member=server-2, GemFire:type=Member,member=server-2, GemFire:service=Region,name="/test-region-1",type=Member,member=server-3, GemFire:service=CacheServer,port=42671,type=Member,member=server-3, GemFire:type=Member,member=server-3]> Expected was: <[GemFire:service=Region,name="/test-region-1",type=Distributed, GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed, GemFire:service=AccessControl,type=Distributed, GemFire:service=FileUploader,type=Distributed, GemFire:service=System,type=Distributed, GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-two, GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-two, GemFire:service=Locator,type=Member,member=locator-two, GemFire:type=Member,member=locator-two, GemFire:service=Region,name="/test-region-1",type=Member,member=server-2, GemFire:service=CacheServer,port=43093,type=Member,member=server-2, GemFire:type=Member,member=server-2, GemFire:service=Region,name="/test-region-1",type=Member,member=server-3, GemFire:service=CacheServer,port=42671,type=Member,member=server-3, GemFire:type=Member,member=server-3]> at org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:158) 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40) at org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) at org.gradle.api.internal.tasks.testing.junit.JUnitTest
[jira] [Commented] (GEODE-5498) JMXMBeanReconnectDUnitTest disconnect and reconnect of members fails
[ https://issues.apache.org/jira/browse/GEODE-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562528#comment-16562528 ] Helena Bales commented on GEODE-5498: - These failures appear to be due to the disconnect/reconnect process on the ClusterStartupRule being flaky. The disconnect command should have a matching "waitForMemberToFinishDisconnecting" (or something to that end). > JMXMBeanReconnectDUnitTest disconnect and reconnect of members fails > > > Key: GEODE-5498 > URL: https://issues.apache.org/jira/browse/GEODE-5498 > Project: Geode > Issue Type: Bug >Reporter: Helena Bales >Priority: Major > Labels: swat > > JMXMBeanReconnectDUnitTest > > testRemoteBeanKnowledge_MaintainServerAndCrashLocator > {{java.lang.AssertionError: > Actual and expected should have same size but actual size was: > <19> > while expected size was: > <15> > Actual was: > <[GemFire:service=Region,name="/test-region-1",type=Distributed, > GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed, > GemFire:service=AccessControl,type=Distributed, > GemFire:service=FileUploader,type=Distributed, > GemFire:service=System,type=Distributed, > > GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-one, > > GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-one, > GemFire:service=Locator,type=Member,member=locator-one, > GemFire:type=Member,member=locator-one, > > GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-two, > > GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-two, > GemFire:service=Locator,type=Member,member=locator-two, > GemFire:type=Member,member=locator-two, > GemFire:service=Region,name="/test-region-1",type=Member,member=server-2, > GemFire:service=CacheServer,port=43093,type=Member,member=server-2, > GemFire:type=Member,member=server-2, > GemFire:service=Region,name="/test-region-1",type=Member,member=server-3, > GemFire:service=CacheServer,port=42671,type=Member,member=server-3, > GemFire:type=Member,member=server-3]> > Expected was: > <[GemFire:service=Region,name="/test-region-1",type=Distributed, > GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Distributed, > GemFire:service=AccessControl,type=Distributed, > GemFire:service=FileUploader,type=Distributed, > GemFire:service=System,type=Distributed, > > GemFire:service=LockService,name=__CLUSTER_CONFIG_LS,type=Member,member=locator-two, > > GemFire:service=DiskStore,name=cluster_config,type=Member,member=locator-two, > GemFire:service=Locator,type=Member,member=locator-two, > GemFire:type=Member,member=locator-two, > GemFire:service=Region,name="/test-region-1",type=Member,member=server-2, > GemFire:service=CacheServer,port=43093,type=Member,member=server-2, > GemFire:type=Member,member=server-2, > GemFire:service=Region,name="/test-region-1",type=Member,member=server-3, > GemFire:service=CacheServer,port=42671,type=Member,member=server-3, > GemFire:type=Member,member=server-3]> > at > org.apache.geode.management.JMXMBeanReconnectDUnitTest.testRemoteBeanKnowledge_MaintainServerAndCrashLocator(JMXMBeanReconnectDUnitTest.java:158) > 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 > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40) > at > org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:40) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.jav
[jira] [Commented] (GEODE-5490) Move backwards compatibility tests to updateTest source set and split up
[ https://issues.apache.org/jira/browse/GEODE-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562529#comment-16562529 ] ASF subversion and git services commented on GEODE-5490: Commit 27f4408d1d6f8d0ebb3c9666113e783d239fca50 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=27f4408 ] GEODE-5490: Update metrics to drop flaky and include upgrade test. > Move backwards compatibility tests to updateTest source set and split up > > > Key: GEODE-5490 > URL: https://issues.apache.org/jira/browse/GEODE-5490 > Project: Geode > Issue Type: Improvement >Reporter: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Improve distributed test runs by moving and splitting up backwards > compatibility tests. Make each test its own test class to improve parallel > execution. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-5325) SUPERFLAKY: PersistentPartitionedRegionDistributedTest.recoversFromCloseDuringRegionOperation fails intermittently
[ https://issues.apache.org/jira/browse/GEODE-5325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Helena Bales resolved GEODE-5325. - Resolution: Fixed Fix Version/s: 1.8.0 > 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 >Assignee: Helena Bales >Priority: Minor > Labels: CI, Flaky, pull-request-available, swat > Fix For: 1.8.0 > > Time Spent: 20m > Remaining Estimate: 0h > > {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] [Commented] (GEODE-4359) Remove std::enable_shared_from_this from PdxSerializable
[ https://issues.apache.org/jira/browse/GEODE-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562537#comment-16562537 ] ASF subversion and git services commented on GEODE-4359: Commit ee6547fae2f89c25c7f0ab524c05f56d4bec1a4d in geode-native's branch refs/heads/develop from [~bbender] [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=ee6547f ] GEODE-4359: Remove enable_shared_from_this (#320) * Remove enable_shared_from_this from PdxSerializable by requiring std::shared_ptr at top API level Co-authored-by: Jacob Barrett > Remove std::enable_shared_from_this from PdxSerializable > > > Key: GEODE-4359 > URL: https://issues.apache.org/jira/browse/GEODE-4359 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob S. Barrett >Priority: Major > > Internal serialization behavior requires that PdxSerializable classes extend > std::enable_shared_from_this. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5499) SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror
Dan Smith created GEODE-5499: Summary: SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror Key: GEODE-5499 URL: https://issues.apache.org/jira/browse/GEODE-5499 Project: Geode Issue Type: Bug Reporter: Dan Smith This test is failing fairly frequently in CI {noformat} org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest: 6 failures (98.101% success rate) | .testTXRmtMirror: 6 failures (98.101% success rate) | | Failed build 315 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/315 | | Failed build 296 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/296 | | Failed build 233 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/233 | | Failed build 123 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/123 | | Failed build 84 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/84 | | Failed build 51 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/51 {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5499) SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror
[ https://issues.apache.org/jira/browse/GEODE-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5499: - Attachment: Test results - Class org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest.html > SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror > -- > > Key: GEODE-5499 > URL: https://issues.apache.org/jira/browse/GEODE-5499 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Priority: Major > Labels: swat > Attachments: Test results - Class > org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest.html > > > This test is failing fairly frequently in CI > {noformat} > org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest: 6 failures > (98.101% success rate) > | .testTXRmtMirror: 6 failures (98.101% success rate) > | | Failed build 315 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/315 > | | Failed build 296 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/296 > | | Failed build 233 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/233 > | | Failed build 123 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/123 > | | Failed build 84 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/84 > | | Failed build 51 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/51 > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5499) SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror
[ https://issues.apache.org/jira/browse/GEODE-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5499: - Labels: swat (was: ) > SUPERFLAKY: DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror > -- > > Key: GEODE-5499 > URL: https://issues.apache.org/jira/browse/GEODE-5499 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Priority: Major > Labels: swat > Attachments: Test results - Class > org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest.html > > > This test is failing fairly frequently in CI > {noformat} > org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest: 6 failures > (98.101% success rate) > | .testTXRmtMirror: 6 failures (98.101% success rate) > | | Failed build 315 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/315 > | | Failed build 296 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/296 > | | Failed build 233 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/233 > | | Failed build 123 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/123 > | | Failed build 84 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/84 > | | Failed build 51 at > https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/51 > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5497) BackupIntegrationTest should be testing incremental backups
[ https://issues.apache.org/jira/browse/GEODE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562613#comment-16562613 ] ASF subversion and git services commented on GEODE-5497: Commit 625f3f21fd52756d8994fa3ce0458400f8d9b549 in geode's branch refs/heads/feature/GEODE-5212 from [~jens.deppe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=625f3f2 ] GEODE-5497: Add an incremental backup test to BackupIntegrationTest (cherry picked from commit 19a0718c501ec116f867c2b731d99db7a0644ac6) > BackupIntegrationTest should be testing incremental backups > --- > > Key: GEODE-5497 > URL: https://issues.apache.org/jira/browse/GEODE-5497 > Project: Geode > Issue Type: Test > Components: regions >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Add a test which validates the generated {{restore,sh}} script for > incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-3720) CI Failure: ConnectCommandWithSSLTest failed
[ https://issues.apache.org/jira/browse/GEODE-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562614#comment-16562614 ] Dan Smith commented on GEODE-3720: -- This most recent failure seems to be happening fairly frequently. In 300 runs: {noformat} org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest: 6 failures (98.101% success rate) | .connectWithNoSSL: 1 failures (99.684% success rate) | | Failed build 128 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/128 | .connectWithJmxSSL: 5 failures (98.418% success rate) | | Failed build 252 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/252 | | Failed build 222 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/222 | | Failed build 149 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/149 | | Failed build 148 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/148 | | Failed build 115 at https://concourse.apachegeode-ci.info/teams/staging/pipelines/mhansonp-pipelinework/jobs/DistributedTest/builds/115 {noformat} > CI Failure: ConnectCommandWithSSLTest failed > > > Key: GEODE-3720 > URL: https://issues.apache.org/jira/browse/GEODE-3720 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.2.1 >Reporter: Jinmei Liao >Assignee: Kenneth Howe >Priority: Major > Labels: ci, pull-request-available > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.html > > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSL(ConnectCommandWithSSLTest.java:198) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithNoSSL(ConnectCommandWithSSLTest.java:177) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterAndJmxSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterAndJmxSSL(ConnectCommandWithSSLTest.java:309) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSLAndThenWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSLAndThenWithNoSSL(ConnectCommandWithSSLTest.java:320) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithHttpSSLAndSkipSSLValidation FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.r
[jira] [Updated] (GEODE-3720) CI Failure: ConnectCommandWithSSLTest failed
[ https://issues.apache.org/jira/browse/GEODE-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-3720: - Attachment: Test results - Class org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.html > CI Failure: ConnectCommandWithSSLTest failed > > > Key: GEODE-3720 > URL: https://issues.apache.org/jira/browse/GEODE-3720 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.2.1 >Reporter: Jinmei Liao >Assignee: Kenneth Howe >Priority: Major > Labels: ci, pull-request-available > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.html > > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSL(ConnectCommandWithSSLTest.java:198) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithNoSSL(ConnectCommandWithSSLTest.java:177) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterAndJmxSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterAndJmxSSL(ConnectCommandWithSSLTest.java:309) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSLAndThenWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSLAndThenWithNoSSL(ConnectCommandWithSSLTest.java:320) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithHttpSSLAndSkipSSLValidation FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithHttpSSLAndSkipSSLValidation(ConnectCommandWithSSLTest.java:286) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterSSL(ConnectCommandWithSSLTest.java:246) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithJmxSSL FAILED > java.lang.Assert
[jira] [Created] (GEODE-5500) retry start_instance task on failure
Finn Southerland created GEODE-5500: --- Summary: retry start_instance task on failure Key: GEODE-5500 URL: https://issues.apache.org/jira/browse/GEODE-5500 Project: Geode Issue Type: Task Reporter: Finn Southerland Especially if we fail to start an instance because CPU quota is exceeded, we should try again in a few minutes, rather than simply fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5451) SUPERFLAKY: LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure fails intermittently
[ https://issues.apache.org/jira/browse/GEODE-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5451: -- Labels: pull-request-available swat (was: swat) > SUPERFLAKY: LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure > fails intermittently > -- > > Key: GEODE-5451 > URL: https://issues.apache.org/jira/browse/GEODE-5451 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Jens Deppe >Assignee: Brian Rowe >Priority: Major > Labels: pull-request-available, swat > Attachments: Test results - Class > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.html > > > Saw the following failure in a precheckin run: > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$109/561146633.run > in VM -2 running on Host e3827a7d1083 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219){noformat} > Test results can be found here: > http://files.apachegeode-ci.info/builds/geode-pr-2153/test-results/disitributedTest/1531949620/ > http://files.apachegeode-ci.info/builds/geode-pr-2153/test-artifacts/1531949620/distributedtesteverythingelse-geode-pr-2153.tgz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5500) retry start_instance task on failure
[ https://issues.apache.org/jira/browse/GEODE-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5500: -- Labels: pull-request-available (was: ) > retry start_instance task on failure > > > Key: GEODE-5500 > URL: https://issues.apache.org/jira/browse/GEODE-5500 > Project: Geode > Issue Type: Task >Reporter: Finn Southerland >Priority: Major > Labels: pull-request-available > > Especially if we fail to start an instance because CPU quota is exceeded, we > should try again in a few minutes, rather than simply fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-3720) CI Failure: ConnectCommandWithSSLTest failed
[ https://issues.apache.org/jira/browse/GEODE-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-3720: - Labels: ci pull-request-available swat (was: ci pull-request-available) > CI Failure: ConnectCommandWithSSLTest failed > > > Key: GEODE-3720 > URL: https://issues.apache.org/jira/browse/GEODE-3720 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.2.1 >Reporter: Jinmei Liao >Assignee: Kenneth Howe >Priority: Major > Labels: ci, pull-request-available, swat > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.html > > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSL(ConnectCommandWithSSLTest.java:198) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithNoSSL(ConnectCommandWithSSLTest.java:177) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterAndJmxSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterAndJmxSSL(ConnectCommandWithSSLTest.java:309) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSLAndThenWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSLAndThenWithNoSSL(ConnectCommandWithSSLTest.java:320) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithHttpSSLAndSkipSSLValidation FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithHttpSSLAndSkipSSLValidation(ConnectCommandWithSSLTest.java:286) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterSSL(ConnectCommandWithSSLTest.java:246) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithJmxSSL FAILED > java.lang.AssertionError: > Expecting: > <
[jira] [Assigned] (GEODE-3720) CI Failure: ConnectCommandWithSSLTest failed
[ https://issues.apache.org/jira/browse/GEODE-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-3720: Assignee: (was: Kenneth Howe) > CI Failure: ConnectCommandWithSSLTest failed > > > Key: GEODE-3720 > URL: https://issues.apache.org/jira/browse/GEODE-3720 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.2.1 >Reporter: Jinmei Liao >Priority: Major > Labels: ci, pull-request-available, swat > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.html > > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSL(ConnectCommandWithSSLTest.java:198) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithNoSSL(ConnectCommandWithSSLTest.java:177) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterAndJmxSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterAndJmxSSL(ConnectCommandWithSSLTest.java:309) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSLAndThenWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSLAndThenWithNoSSL(ConnectCommandWithSSLTest.java:320) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithHttpSSLAndSkipSSLValidation FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithHttpSSLAndSkipSSLValidation(ConnectCommandWithSSLTest.java:286) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterSSL(ConnectCommandWithSSLTest.java:246) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithJmxSSL FAILED > java.lang.AssertionError: > Expecting: > <"_ __ >/ _/ __/
[jira] [Updated] (GEODE-3720) SUPERFLAKY: ConnectCommandWithSSLTest failed
[ https://issues.apache.org/jira/browse/GEODE-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-3720: - Summary: SUPERFLAKY: ConnectCommandWithSSLTest failed (was: CI Failure: ConnectCommandWithSSLTest failed) > SUPERFLAKY: ConnectCommandWithSSLTest failed > > > Key: GEODE-3720 > URL: https://issues.apache.org/jira/browse/GEODE-3720 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.2.1 >Reporter: Jinmei Liao >Priority: Major > Labels: ci, pull-request-available, swat > Attachments: Test results - Class > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.html > > Time Spent: 20m > Remaining Estimate: 0h > > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSL(ConnectCommandWithSSLTest.java:198) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithNoSSL(ConnectCommandWithSSLTest.java:177) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterAndJmxSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterAndJmxSSL(ConnectCommandWithSSLTest.java:309) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithSSLAndThenWithNoSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithSSLAndThenWithNoSSL(ConnectCommandWithSSLTest.java:320) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithHttpSSLAndSkipSSLValidation FAILED > org.junit.ComparisonFailure: expected:<[fals]e> but was:<[tru]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithHttpSSLAndSkipSSLValidation(ConnectCommandWithSSLTest.java:286) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithClusterSSL FAILED > org.junit.ComparisonFailure: expected:<[tru]e> but was:<[fals]e> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest.connectWithClusterSSL(ConnectCommandWithSSLTest.java:246) > org.apache.geode.management.internal.cli.commands.ConnectCommandWithSSLTest > > connectWithJmxSSL FAILED > java.lang.AssertionError: > Expecting: > <"
[jira] [Updated] (GEODE-5482) Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure
[ https://issues.apache.org/jira/browse/GEODE-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5482: - Labels: flaky (was: flaky swat) > Flaky test LocatorConnectionDUnitTest > testInvalidOperationReturnsFailure > -- > > Key: GEODE-5482 > URL: https://issues.apache.org/jira/browse/GEODE-5482 > Project: Geode > Issue Type: Bug > Components: tests >Affects Versions: 1.8.0 >Reporter: Jacob S. Barrett >Priority: Major > Labels: flaky > > {noformat} > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest > > testInvalidOperationReturnsFailure FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest$$Lambda$112/1065764231.run > in VM -2 running on Host d0a2838cf5a3 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.validateStats(LocatorConnectionDUnitTest.java:217) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.testInvalidOperationReturnsFailure(LocatorConnectionDUnitTest.java:144) > Caused by: > java.lang.AssertionError: expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.geode.internal.protocol.protobuf.v1.acceptance.LocatorConnectionDUnitTest.lambda$validateStats$c7642ca0$1(LocatorConnectionDUnitTest.java:219) > {noformat} > See failed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/156#L5b4cf8d7:1404 > See passed: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/155#L5b59f1be:1388 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates(
[ https://issues.apache.org/jira/browse/GEODE-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5501: - Labels: swat (was: ) > CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates( > - > > Key: GEODE-5501 > URL: https://issues.apache.org/jira/browse/GEODE-5501 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Priority: Major > Labels: swat > > {noformat} > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0 > running on Host 4fad81dffa5f with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:425) > at > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57) > 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 > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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 > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy1.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) > 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) >
[jira] [Updated] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates
[ https://issues.apache.org/jira/browse/GEODE-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5501: - Summary: CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates (was: CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates() > CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates > > > Key: GEODE-5501 > URL: https://issues.apache.org/jira/browse/GEODE-5501 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: swat > > {noformat} > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0 > running on Host 4fad81dffa5f with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:425) > at > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57) > 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 > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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 > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy1.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
[jira] [Assigned] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates(
[ https://issues.apache.org/jira/browse/GEODE-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-5501: Assignee: Dan Smith > CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates( > - > > Key: GEODE-5501 > URL: https://issues.apache.org/jira/browse/GEODE-5501 > Project: Geode > Issue Type: Bug >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Labels: swat > > {noformat} > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0 > running on Host 4fad81dffa5f with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:425) > at > org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57) > 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 > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) > at > org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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 > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy1.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) > 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.re
[jira] [Created] (GEODE-5501) CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates(
Dan Smith created GEODE-5501: Summary: CI Failure: NetSearchMessagingDUnitTest.testOneMessageWithReplicates( Key: GEODE-5501 URL: https://issues.apache.org/jira/browse/GEODE-5501 Project: Geode Issue Type: Bug Reporter: Dan Smith {noformat} org.apache.geode.test.dunit.RMIException: While invoking org.apache.geode.internal.cache.NetSearchMessagingDUnitTest$14.run in VM 0 running on Host 4fad81dffa5f with 4 VMs at org.apache.geode.test.dunit.VM.invoke(VM.java:443) at org.apache.geode.test.dunit.VM.invoke(VM.java:412) at org.apache.geode.test.dunit.VM.invoke(VM.java:355) at org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.createReplicate(NetSearchMessagingDUnitTest.java:425) at org.apache.geode.internal.cache.NetSearchMessagingDUnitTest.testOneMessageWithReplicates(NetSearchMessagingDUnitTest.java:57) 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 org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:106) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:58) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.execute(JUnitTestClassExecutor.java:38) at org.gradle.api.internal.tasks.testing.junit.AbstractJUnitTestClassProcessor.processTestClass(AbstractJUnitTestClassProcessor.java:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) 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 org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) at org.gradle.internal.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) at com.sun.proxy.$Proxy1.processTestClass(Unknown Source) at org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:109) 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 org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.internal.remote.internal.hub.MessageHubBackedObjectConnection$DispatchWrapper.dispatch(MessageHubBackedObjectConn
[jira] [Resolved] (GEODE-2072) CI Failure: TestFunctionsDUnitTest.testNumOfRunningFunctions
[ https://issues.apache.org/jira/browse/GEODE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-2072. -- Resolution: Duplicate > CI Failure: TestFunctionsDUnitTest.testNumOfRunningFunctions > > > Key: GEODE-2072 > URL: https://issues.apache.org/jira/browse/GEODE-2072 > Project: Geode > Issue Type: Bug > Components: management, tests >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Priority: Major > Labels: CI, Flaky > Attachments: Test results - Class > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.html > > > {noformat} > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest > > testNumOfRunningFunctions FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest$$Lambda$15/1807889435.call > in VM 0 running on Host a00f4285b6a8 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:344) > at org.apache.geode.test.dunit.VM.invoke(VM.java:314) > at org.apache.geode.test.dunit.VM.invoke(VM.java:282) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.testNumOfRunningFunctions(TestFunctionsDUnitTest.java:100) > Caused by: > java.lang.AssertionError: Event never occurred after 12 ms: wait > for getNumOfRunningFunction to complete and get results > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.getNumOfRunningFunction(TestFunctionsDUnitTest.java:77) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.lambda$testNumOfRunningFunctions$5c4d653a$1(TestFunctionsDUnitTest.java:100) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-2072) CI Failure: TestFunctionsDUnitTest.testNumOfRunningFunctions
[ https://issues.apache.org/jira/browse/GEODE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-2072: - Component/s: (was: swat) > CI Failure: TestFunctionsDUnitTest.testNumOfRunningFunctions > > > Key: GEODE-2072 > URL: https://issues.apache.org/jira/browse/GEODE-2072 > Project: Geode > Issue Type: Bug > Components: management, tests >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Priority: Major > Labels: CI, Flaky > Attachments: Test results - Class > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.html > > > {noformat} > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest > > testNumOfRunningFunctions FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest$$Lambda$15/1807889435.call > in VM 0 running on Host a00f4285b6a8 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:344) > at org.apache.geode.test.dunit.VM.invoke(VM.java:314) > at org.apache.geode.test.dunit.VM.invoke(VM.java:282) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.testNumOfRunningFunctions(TestFunctionsDUnitTest.java:100) > Caused by: > java.lang.AssertionError: Event never occurred after 12 ms: wait > for getNumOfRunningFunction to complete and get results > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.getNumOfRunningFunction(TestFunctionsDUnitTest.java:77) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.lambda$testNumOfRunningFunctions$5c4d653a$1(TestFunctionsDUnitTest.java:100) > {noformat} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5460) SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions
[ https://issues.apache.org/jira/browse/GEODE-5460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-5460: - Summary: SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions (was: Flaky test TestFunctionsDUnitTest.testNumOfRunningFunctions) > SUPERFLAKY: TestFunctionsDUnitTest.testNumOfRunningFunctions > > > Key: GEODE-5460 > URL: https://issues.apache.org/jira/browse/GEODE-5460 > Project: Geode > Issue Type: Bug >Reporter: Helena Bales >Priority: Major > Labels: ci, flaky, swat > > {{org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest > > testNumOfRunningFunctions FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest$$Lambda$29/242148781.call > in VM 0 running on Host 57e1ae1f71ab with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:443) > at org.apache.geode.test.dunit.VM.invoke(VM.java:412) > at org.apache.geode.test.dunit.VM.invoke(VM.java:378) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.testNumOfRunningFunctions(TestFunctionsDUnitTest.java:94) > Caused by: > java.lang.AssertionError: Event never occurred after 12 ms: wait > for getNumOfRunningFunction to complete and get results > at org.junit.Assert.fail(Assert.java:88) > at > org.apache.geode.test.dunit.Wait.waitForCriterion(Wait.java:190) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.getNumOfRunningFunction(TestFunctionsDUnitTest.java:71) > at > org.apache.geode.management.internal.pulse.TestFunctionsDUnitTest.lambda$testNumOfRunningFunctions$5c4d653a$1(TestFunctionsDUnitTest.java:94) > }} -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-5502) Cluster configuration can contain member-specific gateway receiver definitions which cause members to fail to start during rolling
[ https://issues.apache.org/jira/browse/GEODE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby reassigned GEODE-5502: Assignee: Barry Oglesby > Cluster configuration can contain member-specific gateway receiver > definitions which cause members to fail to start during rolling > -- > > Key: GEODE-5502 > URL: https://issues.apache.org/jira/browse/GEODE-5502 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Barry Oglesby >Assignee: Barry Oglesby >Priority: Major > Labels: swat > > In versions before 1.4.0, cluster configuration could contain multiple > member-specific gateway receiver definitions like: > {noformat} > > > > > {noformat} > Starting in 1.4.0, multiple receivers are no longer allowed, so a > configuration like this causes the member to throw an exception and fail to > start. > These member-specific receivers should be removed before sending the cluster > configuration to new members to avoid attempting to create multiple receivers > in a single member. > Note: In this case, the member will start with no receivers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5502) Cluster configuration can contain member-specific gateway receiver definitions which cause members to fail to start during rolling
Barry Oglesby created GEODE-5502: Summary: Cluster configuration can contain member-specific gateway receiver definitions which cause members to fail to start during rolling Key: GEODE-5502 URL: https://issues.apache.org/jira/browse/GEODE-5502 Project: Geode Issue Type: Bug Components: configuration Reporter: Barry Oglesby In versions before 1.4.0, cluster configuration could contain multiple member-specific gateway receiver definitions like: {noformat} {noformat} Starting in 1.4.0, multiple receivers are no longer allowed, so a configuration like this causes the member to throw an exception and fail to start. These member-specific receivers should be removed before sending the cluster configuration to new members to avoid attempting to create multiple receivers in a single member. Note: In this case, the member will start with no receivers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5502) Cluster configuration can contain member-specific gateway receiver definitions which cause members to fail to start during rolling
[ https://issues.apache.org/jira/browse/GEODE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barry Oglesby updated GEODE-5502: - Labels: swat (was: ) > Cluster configuration can contain member-specific gateway receiver > definitions which cause members to fail to start during rolling > -- > > Key: GEODE-5502 > URL: https://issues.apache.org/jira/browse/GEODE-5502 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Barry Oglesby >Assignee: Barry Oglesby >Priority: Major > Labels: swat > > In versions before 1.4.0, cluster configuration could contain multiple > member-specific gateway receiver definitions like: > {noformat} > > > > > {noformat} > Starting in 1.4.0, multiple receivers are no longer allowed, so a > configuration like this causes the member to throw an exception and fail to > start. > These member-specific receivers should be removed before sending the cluster > configuration to new members to avoid attempting to create multiple receivers > in a single member. > Note: In this case, the member will start with no receivers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5502) Cluster configuration can contain member-specific gateway receiver definitions which cause members to fail to start during rolling
[ https://issues.apache.org/jira/browse/GEODE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-5502: -- Labels: pull-request-available swat (was: swat) > Cluster configuration can contain member-specific gateway receiver > definitions which cause members to fail to start during rolling > -- > > Key: GEODE-5502 > URL: https://issues.apache.org/jira/browse/GEODE-5502 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Barry Oglesby >Assignee: Barry Oglesby >Priority: Major > Labels: pull-request-available, swat > > In versions before 1.4.0, cluster configuration could contain multiple > member-specific gateway receiver definitions like: > {noformat} > > > > > {noformat} > Starting in 1.4.0, multiple receivers are no longer allowed, so a > configuration like this causes the member to throw an exception and fail to > start. > These member-specific receivers should be removed before sending the cluster > configuration to new members to avoid attempting to create multiple receivers > in a single member. > Note: In this case, the member will start with no receivers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5497) Generated backup.sh script is incorrect and fails when incremental backups are restored
[ https://issues.apache.org/jira/browse/GEODE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe updated GEODE-5497: -- Issue Type: Bug (was: Test) > Generated backup.sh script is incorrect and fails when incremental backups > are restored > > > Key: GEODE-5497 > URL: https://issues.apache.org/jira/browse/GEODE-5497 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Add a test which validates the generated {{restore,sh}} script for > incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5497) Generated backup.sh script is incorrect and fails when incremental backups are restored
[ https://issues.apache.org/jira/browse/GEODE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe updated GEODE-5497: -- Summary: Generated backup.sh script is incorrect and fails when incremental backups are restored (was: BackupIntegrationTest should be testing incremental backups) > Generated backup.sh script is incorrect and fails when incremental backups > are restored > > > Key: GEODE-5497 > URL: https://issues.apache.org/jira/browse/GEODE-5497 > Project: Geode > Issue Type: Test > Components: regions >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Add a test which validates the generated {{restore,sh}} script for > incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5497) Generated backup.sh script is incorrect and fails when incremental backups are restored
[ https://issues.apache.org/jira/browse/GEODE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562986#comment-16562986 ] Jens Deppe commented on GEODE-5497: --- When restoring incremental backups the generated {{restore.sh}} script may fail with the following error: {noformat} [info 2018/07/30 18:48:12.272 PDT tid=1] GemFireCache[id = 797724590; isClosing = true; isShutDownAll = false; created = Mon Jul 30 18:48:11 PDT 2018; server = false; copyOnRead = false; lockLease = 120; lockTimeout = 60]: Now closing. [info 2018/07/30 18:48:12.273 PDT tid=1] Created oplog#13 krf for disk store diskStore. EXECUTING:/private/var/folders/vp/5bj0m2lj1qx63v202sjr5xm8gp/T/junit358337362196747300/incremental/2018-07-30-18-48-11/deppe-mbp-35878-loner--0-177005ee/restore.sh OUTPUT:cp: /var/folders/vp/5bj0m2lj1qx63v202sjr5xm8gp/T/junit358337362196747300/disk_Dir2/BACKUPdiskStore_6.drf: No such file or directory {noformat} The generated script has two main sections - one that restores all base files and directories and one that copies files from an incremental backup. The problem is that the second step does not create any necessary directories and the file copy fails. This problem was exposed after GEODE-5463 was fixed. That change removed the creation of extraneous directories which masked the issue. > Generated backup.sh script is incorrect and fails when incremental backups > are restored > > > Key: GEODE-5497 > URL: https://issues.apache.org/jira/browse/GEODE-5497 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Add a test which validates the generated {{restore,sh}} script for > incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5497) Generated backup.sh script fails when incremental backups are restored
[ https://issues.apache.org/jira/browse/GEODE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe updated GEODE-5497: -- Summary: Generated backup.sh script fails when incremental backups are restored (was: Generated backup.sh script is incorrect and fails when incremental backups are restored ) > Generated backup.sh script fails when incremental backups are restored > --- > > Key: GEODE-5497 > URL: https://issues.apache.org/jira/browse/GEODE-5497 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Add a test which validates the generated {{restore,sh}} script for > incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-5497) Generated restore.sh script fails when incremental backups are restored
[ https://issues.apache.org/jira/browse/GEODE-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe updated GEODE-5497: -- Summary: Generated restore.sh script fails when incremental backups are restored (was: Generated backup.sh script fails when incremental backups are restored ) > Generated restore.sh script fails when incremental backups are restored > > > Key: GEODE-5497 > URL: https://issues.apache.org/jira/browse/GEODE-5497 > Project: Geode > Issue Type: Bug > Components: regions >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Time Spent: 50m > Remaining Estimate: 0h > > Add a test which validates the generated {{restore,sh}} script for > incremental backups. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
Jacob S. Barrett created GEODE-5503: --- Summary: Reduce CI overhead on pull request to decrease feedback time. Key: GEODE-5503 URL: https://issues.apache.org/jira/browse/GEODE-5503 Project: Geode Issue Type: Improvement Components: ci Reporter: Jacob S. Barrett Reorganize and reduce overhead in the CI pull request pipeline to give faster feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563004#comment-16563004 ] ASF subversion and git services commented on GEODE-5503: Commit 49e02eb1e7f252e12dd0a15662b2fac4ffb29c38 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=49e02eb ] GEODE-5503: Reorganized to decrease overhead wait times. > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563005#comment-16563005 ] ASF subversion and git services commented on GEODE-5503: Commit 6387e1b0dec331b87b281895f1b2ce496f259cac in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6387e1b ] GEODE-5503: Fixes resource name. > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563050#comment-16563050 ] ASF subversion and git services commented on GEODE-5503: Commit 24c4e23aaae9d98ee407a63d7d1b205580267420 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=24c4e23 ] GEODE-5503: Use image_resource > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563057#comment-16563057 ] ASF subversion and git services commented on GEODE-5503: Commit b05835ba39437d3a5071838a97931f56e81c8006 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b05835b ] GEODE-5503: Fixes image_resource > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563059#comment-16563059 ] ASF subversion and git services commented on GEODE-5503: Commit 2a8bf0fd15f92f3eb5b22c60d75ad11bba3cb78e in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=2a8bf0f ] GEODE-5503: Fixes image_resource > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563076#comment-16563076 ] ASF subversion and git services commented on GEODE-5503: Commit 7af0669c34fc9a718546e6a66a48f029c4457057 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7af0669 ] GEODE-5503: Reduce overhead wait time on main pipeline. > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563093#comment-16563093 ] ASF subversion and git services commented on GEODE-5503: Commit 1ee91d27ac3e19ac775ca6197726bb7e9d59bdb6 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1ee91d2 ] GEODE-5503: Fixes dependency ordering. > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563108#comment-16563108 ] ASF subversion and git services commented on GEODE-5503: Commit 1cab7cb51bbb4d9c33f0e3ec728775c9ac8a3f5d in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1cab7cb ] GEODE-5503: Remove prepopulate_build since parallel build is fixed. > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-5503) Reduce CI overhead on pull request to decrease feedback time.
[ https://issues.apache.org/jira/browse/GEODE-5503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563119#comment-16563119 ] ASF subversion and git services commented on GEODE-5503: Commit d898662b7acdc8ec2fdaedbc065d3670a271eab5 in geode's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d898662 ] GEODE-5503: Fixes resource dependency ordering. > Reduce CI overhead on pull request to decrease feedback time. > - > > Key: GEODE-5503 > URL: https://issues.apache.org/jira/browse/GEODE-5503 > Project: Geode > Issue Type: Improvement > Components: ci >Reporter: Jacob S. Barrett >Priority: Major > > Reorganize and reduce overhead in the CI pull request pipeline to give faster > feedback. -- This message was sent by Atlassian JIRA (v7.6.3#76005)