suztomo edited a comment on pull request #14474: URL: https://github.com/apache/beam/pull/14474#issuecomment-816871115
Another case https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/17051/. With `org.gradle.caching=false`, the build console stopped showing progress after 1 hour 16 minutes. With jstack, I got following stacktraces: https://gist.github.com/suztomo/7757ac7b1df2ad33934bb51adcc8f375 ``` 14:16:35 "pool-123-thread-1" #179 prio=5 os_prio=0 tid=0x00007f3ee0ed6000 nid=0x4bd waiting on condition [0x00007f3e8e0e9000] 14:16:35 java.lang.Thread.State: WAITING (parking) 14:16:35 at sun.misc.Unsafe.park(Native Method) 14:16:35 - parking to wait for <0x00000000e4f96648> (a java.util.concurrent.CountDownLatch$Sync) 14:16:35 at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) 14:16:35 at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) 14:16:35 at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997) 14:16:35 at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304) 14:16:35 at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231) 14:16:35 at org.apache.beam.runners.fnexecution.logging.GrpcLoggingServiceTest.lambda$testMultipleClientsFailingIsHandledGracefullyByServer$2(GrpcLoggingServiceTest.java:122) 14:16:35 at org.apache.beam.runners.fnexecution.logging.GrpcLoggingServiceTest$$Lambda$425/31993368.call(Unknown Source) ``` ``` 14:16:35 at java.util.concurrent.AbstractExecutorService.invokeAll(AbstractExecutorService.java:244) 14:16:35 at org.apache.beam.runners.fnexecution.logging.GrpcLoggingServiceTest.testMultipleClientsFailingIsHandledGracefullyByServer(GrpcLoggingServiceTest.java:127) ``` Previous one was BeamFnLoggingServiceTest. This one is GrpcLoggingServiceTest. Problem with logging? -- 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: [email protected]
