Re: Geode unit tests 'develop/DistributedTest' took too long to execute
This is yet another test that hung in shutting down the dlock service in a WAN test - Same as https://issues.apache.org/jira/browse/GEODE-4650. -Dan On Fri, Jul 13, 2018 at 2:52 PM, wrote: > Pipeline results can be found at: > > Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/ > develop/jobs/DistributedTest/builds/114 > >
Re: Geode unit tests 'develop/DistributedTest' took too long to execute
These timeouts are due to a hang in a query test that seem to be caused by the pdx-read-serialized work I checked in earlier this week. I'm reverting those changes until I can figure out why this is happening. On 3/27/18 2:12 PM, apachegeod...@gmail.com wrote: Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/227
Re: Geode unit tests 'develop/DistributedTest' took too long to execute
It looks like the CI run hung in a test that I introduced on Friday. I'm looking into it. "RMI TCP Connection(2)-172.17.0.7" #112 daemon prio=5 os_prio=0 tid=0x7f63b0003000 nid=0x333 waiting on condition [0x7f64411cc000] java.lang.Thread.State: TIMED_WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0xf5fab298> (a java.util.concurrent.CountDownLatch$Sync) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328) at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) at org.apache.geode.internal.util.concurrent.StoppableCountDownLatch.await(StoppableCountDownLatch.java:64) at org.apache.geode.distributed.internal.ReplyProcessor21.basicWait(ReplyProcessor21.java:715) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:790) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:766) at org.apache.geode.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:853) at org.apache.geode.distributed.internal.locks.DLockRequestProcessor.requestLock(DLockRequestProcessor.java:236) at org.apache.geode.distributed.internal.locks.DLockService.lockInterruptibly(DLockService.java:1474) at org.apache.geode.distributed.internal.locks.DLockService.lock(DLockService.java:1246) at org.apache.geode.distributed.internal.locks.DLockService.lock(DLockService.java:1237) at org.apache.geode.distributed.internal.locks.DLockService.lock(DLockService.java:1232) at org.apache.geode.distributed.internal.locks.DLockService.lock(DLockService.java:1228) at org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.performOps(DlockAndTxlockRegressionTest.java:185) at org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest.lambda$testDLockProtectsAgainstTransactionConflict$bb17a952$5(DlockAndTxlockRegressionTest.java:116) at org.apache.geode.distributed.internal.DlockAndTxlockRegressionTest$$Lambda$62/139614585.run(Unknown Source) On 3/24/18 5:03 AM, apachegeod...@gmail.com wrote: Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/223
Re: Geode unit tests 'develop/DistributedTest' took too long to execute
I logged a ticket for this hang: https://issues.apache.org/jira/browse/GEODE-4650 From what I can tell, it looks like some sort of race condition where the DLockService is stuck trying to clearGrantor. On Fri, Feb 9, 2018 at 10:20 PMwrote: > Pipeline results can be found at: > > Concourse: > https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/135 > >