You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@geode.apache.org by GitBox <gi...@apache.org> on 2021/03/02 15:39:30 UTC

[GitHub] [geode-native] pdxcodemonkey commented on pull request #713: GEODE-8442: Exception in server not identified correctly in client

pdxcodemonkey commented on pull request #713:
URL: https://github.com/apache/geode-native/pull/713#issuecomment-788999841


   The test output is a little tricky to see clearly, but the issue in this PR is not `RegisterKeysTest.RegisterAllWithConsistencyDisabled`.  If you grep for it, you see the following:
   
   ```
         Start 55: RegisterKeysTest.RegisterAllWithConsistencyDisabled
   18/78 Test #55: RegisterKeysTest.RegisterAllWithConsistencyDisabled ..................................***Failed  152.70 sec
   Note: Google Test filter = RegisterKeysTest.RegisterAllWithConsistencyDisabled
   [ RUN      ] RegisterKeysTest.RegisterAllWithConsistencyDisabled
   [2021-03-01 12:46:10.389389] [0x00002d58] [info]    Gfsh::execute: start locator --log-level=INFO --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/locator/0 --name=RegisterKeysTest_RegisterAllWithConsistencyDisabled_locator_0 --bind-address=localhost --port=50311 --max-heap=256m --J=-Dgemfire.jmx-manager-port=50310 --http-service-port=0 --J=-Dgemfire.jmx-manager-start=true
   [2021-03-01 12:46:15.701819] [0x00002d58] [trace]   Gfsh::execute: (1) Executing - start locator --log-level=INFO --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/locator/0 --name=RegisterKeysTest_RegisterAllWithConsistencyDisabled_locator_0 --bind-address=localhost --port=50311 --max-heap=256m --J=-Dgemfire.jmx-manager-port=50310 --http-service-port=0 --J=-Dgemfire.jmx-manager-start=true
   [2021-03-01 12:46:33.904986] [0x00002d58] [trace]   Gfsh::execute: Locator in C:\Users\build\build\cppcache\integration\test\RegisterKeysTest\RegisterAllWithConsistencyDisabled\locator\0 on 127.0.0.1[50311] as RegisterKeysTest_RegisterAllWithConsistencyDisabled_locator_0 is currently online.
   [2021-03-01 12:46:33.904986] [0x00002d58] [trace]   Gfsh::execute: Log File: C:\Users\build\build\cppcache\integration\test\RegisterKeysTest\RegisterAllWithConsistencyDisabled\locator\0\RegisterKeysTest_RegisterAllWithConsistencyDisabled_locator_0.log
   [2021-03-01 12:46:44.793326] [0x00002d58] [info]    Gfsh::execute: start server --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/server/0 --name=RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[50311]
   [2021-03-01 12:46:55.904964] [0x00002d58] [trace]   Gfsh::execute: (2) Executing - start server --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/server/0 --name=RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0 --bind-address=localhost --server-port=0 --max-heap=1g --locators=localhost[50311]
   [2021-03-01 12:47:10.389461] [0x00002d58] [trace]   Gfsh::execute: Server in C:\Users\build\build\cppcache\integration\test\RegisterKeysTest\RegisterAllWithConsistencyDisabled\server\0 on build-7876be09-a95c-4725-b2d3-4cb99aabd716.c.apachegeode-ci.internal[50533] as RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0 is currently online.
   [2021-03-01 12:47:10.389461] [0x00002d58] [trace]   Gfsh::execute: Log File: C:\Users\build\build\cppcache\integration\test\RegisterKeysTest\RegisterAllWithConsistencyDisabled\server\0\RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0.log
   [2021-03-01 12:47:24.217552] [0x000028ec] [trace]   Gfsh::execute: RegisterKeysTest_RegisterAllWithConsistencyDisabled_server_0 | OK     | Region "/region" created o..
   [2021-03-01 12:48:28.451760] [0x00001b0c] [info]    Gfsh::execute: stop server --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/server/0
   [2021-03-01 12:48:28.451760] [0x000013a4] [info]    Gfsh::execute: stop locator --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/locator/0
   [2021-03-01 12:48:39.288256] [0x00001b0c] [trace]   Gfsh::execute: (2) Executing - stop server --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/server/0
   [2021-03-01 12:48:39.320492] [0x000013a4] [trace]   Gfsh::execute: (2) Executing - stop locator --dir=RegisterKeysTest/RegisterAllWithConsistencyDisabled/locator/0
   [  FAILED  ] RegisterKeysTest.RegisterAllWithConsistencyDisabled (152546 ms)
   [  FAILED  ] RegisterKeysTest.RegisterAllWithConsistencyDisabled
         Start 55: RegisterKeysTest.RegisterAllWithConsistencyDisabled
       Test #55: RegisterKeysTest.RegisterAllWithConsistencyDisabled ..................................   Passed   96.14 sec
   ```
   
   So, that test re-ran and passed the second time.  The problem is that the run is timing out because one test is stuck.  I have a rudimentary Python script that matches the "Start X:" output lines with "Test #X:" result lines, that shows which ones are unmatched, i.e. never completed.  Here's the output from that:
   
   ```
   Passed:
       AuthInitializeTest.putGetWithBasicAuth (#1)
       AuthInitializeTest.putWithBadUsername (#2)
       AuthInitializeTest.putWithBadPassword (#3)
       AuthInitializeTest.badCredentialsWithSubscriptionEnabled (#4)
       CacheWriterTest.WriteInRegionFromCacheWriterTriggeredByTransaction (#6)
       CacheXmlTest.loadCacheXml (#7)
       CacheXmlTest.loadCacheXmlWithBadSchema (#8)
       CacheXmlTest.loadCacheWithUnnamedPool (#9)
       CacheXmlTest.testApplicationPartitionResolver (#10)
       CacheXmlTest.testSharedLibPartitionResolver (#11)
       CleanIdleConnectionsTest.cleanIdleConnectionsAfterOpsPaused (#12)
       ClientTransactionXATest.interTxand2PCTx (#13)
       CommitConflictExceptionTest.putPartitionTx (#14)
       CqPlusAuthInitializeTest.putInALoopWhileSubscribedAndAuthenticated (#15)
       CqTest.testCqCreateUpdateDestroy (#16)
       DataSerializableTest.isSerializableAndDeserializable (#17)
       DataSerializableTest.ClassAsKey (#18)
       ChunkHandlerThreadTest.isDisabledUsesSameThread (#19)
       ChunkHandlerThreadTest.isEnabledUsesDifferentThread (#20)
       ExceptionTranslationTest.testLowMemoryException (#23)
       ExceptionTranslationTest.testQueryLowMemoryException (#24)
       ExpirationTest.verifyExpiration (#25)
       FunctionExecutionTest.UnknownFunctionOnServer (#26)
       FunctionExecutionTest.UnknownFunctionOnRegion (#27)
       FunctionExecutionTest.UnknownFunctionAsyncOnServer (#28)
       FunctionExecutionTest.UnknownFunctionAsyncOnRegion (#29)
       FunctionExecutionTest.FunctionReturnsObjectWhichCantBeDeserializedOnServer (#30)
       FunctionExecutionTest.OnServersWithReplicatedRegionsInPool (#31)
       FunctionExecutionTest.OnServersOneServerGoesDown (#32)
       LRUEvictionTest.heapLruLimit (#33)
       LRUEvictionTest.lruEntriesLimit (#34)
       LRUEvictionTest.verifyLruOrderGet (#35)
       LRUEvictionTest.verifyLruOrderInvalidate (#36)
       LRUEvictionTest.verifyLruOrderDestroy (#37)
       LocatorRequestsTest.verifyNoInterlock (#38)
       PartitionRegionOpsTest.getPartitionedRegionWithRedundancyServerGoesDownSingleHop (#39)
       PartitionRegionOpsTest.putPartitionedRegionWithRedundancyServerGoesDownSingleHop (#40)
       PartitionRegionOpsTest.getPartitionedRegionWithRedundancyServerGoesDownNoSingleHop (#41)
       PartitionRegionOpsTest.putPartitionedRegionWithRedundancyServerGoesDownNoSingleHop (#42)
       PdxInstanceFactoryTest.testConcurrentCreateCalls (#43)
       PdxInstanceTest.testPdxInstance (#44)
       PdxInstanceTest.testCreateJsonInstance (#45)
       PdxJsonTypeTest.testGfshQueryJsonInstances (#46)
       PdxJsonTypeTest.testCreateTwoJsonInstances (#47)
       PdxJsonTypeTest.testTwoConsecutiveGets (#48)
       PdxSerializerTest.canSerializeNonPdxSerializableType (#49)
       RegionGetAllTest.getAllFromPartitionedRegion (#50)
       RegionPutAllTest.putAllToPartitionedRegion (#51)
       RegionPutGetAllTest.variousPdxTypes (#52)
       RegionPutGetAllTest.nullValue (#53)
       RegisterKeysTest.RegisterAllWithCachingRegion (#54)
       RegisterKeysTest.RegisterAllWithConsistencyDisabled (#55)
       RegisterKeysTest.RegisterAnyWithCachingRegion (#56)
       RegisterKeysTest.RegisterAllWithProxyRegion (#57)
       RegisterKeysTest.RegisterAnyWithProxyRegion (#58)
       ServerDisconnect.WithRegionDisconnectedListener (#59)
       SslOneWayTest.PutGetWithValidSslConfiguration (#60)
       SslOneWayTest.PutWithUntrustedTruststore (#61)
       SslOneWayTest.PutWithCorruptTruststore (#62)
       SslOneWayTest.PutWithMissingTruststore (#63)
       SslTwoWayTest.PutGetWithValidSslConfiguration (#64)
       SslTwoWayTest.PutWithInvalidKeystorePassword (#65)
       SslTwoWayTest.PutWithUntrustedKeystore (#66)
       SslTwoWayTest.PutWithCorruptKeystore (#67)
       SslTwoWayTest.PutWithUntrustedTruststore (#68)
       SslTwoWayTest.PutWithCorruptTruststore (#69)
       SslTwoWayTest.PutWithMissingTruststore (#70)
       StructTest.queryResultForRange (#71)
       TransactionCleaningTest.txWithStoppedServer (#72)
       TransactionsTest.ExceptionWhenRollingBackTx (#73)
       TransactionsTest.IlegalStateExceptionNoTx (#74)
       TransactionsTest.ExceptionConflictOnPrepare (#75)
       TransactionsTest.ExceptionConflictOnCommit (#76)
       WanDeserializationTest.testEventsAreDeserializedCorrectly (#77)
   Failed:
       RegisterKeysTest.RegisterAllWithConsistencyDisabled (#55)
   Timed Out:
       None
   Not Run:
       BasicIPv6Test.queryResultForRange (#5)
       ExampleTest.putAndGetWith2Servers (#21)
       ExampleTest.putGetAndUpdateWith1Server (#22)
   Stuck:
       ContainsKeyOnServerExceptionTest.handleException (#78)
   Tests Passed:
       74/76 (97%)
   Tests Failed:
       1/76 (1%)
   Tests Timed Out:
       0/76 (0%)
   Tests Stuck:
       1/76 (1%)
   Tests Not Run:
       3/79 (4%)
   ```
   So it appears the new test for this PR, `ContainsKeyOnServerExceptionTest.handleException`, hangs on Windows. 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org