Valentyn Tymofieiev created BEAM-12859:
------------------------------------------
Summary:
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingServiceTest.testMultipleClientsFailingIsHandledGracefullyByServer
is flaky
Key: BEAM-12859
URL: https://issues.apache.org/jira/browse/BEAM-12859
Project: Beam
Issue Type: Bug
Components: sdk-java-core
Reporter: Valentyn Tymofieiev
As per [prior discussion on
dev|https://lists.apache.org/thread.html/ra75bec744b6184d6576244b6d5e6ac7ca321c74b7c6df4d4d7bdddf1%40%3Cdev.beam.apache.org%3E],
this may have started after upgrading vendored gRPC from 1.26.0 to 1.36.0.
Sample error from
https://ci-beam.apache.org/job/beam_PreCommit_Java_Cron/4469/testReport/junit/org.apache.beam.runners.dataflow.worker.fn.logging/BeamFnLoggingServiceTest/testMultipleClientsFailingIsHandledGracefullyByServer/
{noformat}
Error Message
org.junit.runners.model.TestTimedOutException: test timed out after 5000
milliseconds
Stacktrace
org.junit.runners.model.TestTimedOutException: test timed out after 5000
milliseconds
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
at
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingServiceTest.testMultipleClientsFailingIsHandledGracefullyByServer(BeamFnLoggingServiceTest.java:156)
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:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:288)
at
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:282)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:748)
Standard Error
Sep 07, 2021 12:12:20 AM
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingService <init>
INFO: Launched Beam Fn Logging service url: "127.0.0.1:34883"
Sep 07, 2021 12:12:20 AM
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingService logging
INFO: Beam Fn Logging client connected for client
Sep 07, 2021 12:12:20 AM
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingService logging
INFO: Beam Fn Logging client connected for client
Sep 07, 2021 12:12:20
...[truncated 5654 chars]...
nnected for client
Sep 07, 2021 12:12:20 AM
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingService logging
INFO: Beam Fn Logging client connected for client
Sep 07, 2021 12:12:20 AM
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingService logging
INFO: Beam Fn Logging client connected for client
Sep 07, 2021 12:12:20 AM
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingService close
INFO: 3 Beam Fn Logging clients still connected during shutdown.
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
