You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Daniel Oliveira (JIRA)" <ji...@apache.org> on 2019/01/29 18:54:00 UTC

[jira] [Created] (BEAM-6539) Some Java PostCommits failing: Coder casting error.

Daniel Oliveira created BEAM-6539:
-------------------------------------

             Summary: Some Java PostCommits failing: Coder casting error.
                 Key: BEAM-6539
                 URL: https://issues.apache.org/jira/browse/BEAM-6539
             Project: Beam
          Issue Type: Bug
          Components: test-failures
            Reporter: Daniel Oliveira


_Use this form to file an issue for test failure:_
 * [First Failing Jenkins Job|https://builds.apache.org/job/beam_PostCommit_Java_PortabilityApi/828/]
 * [Gradle Build Scan|https://scans.gradle.com/s/32la4tbaonr5a]

Initial investigation:

This is happening in beam_PostCommit_Java_PortabilityApi and beam_PostCommit_Java_ValidatesRunner_PortabilityApi_Dataflow that I know of. Tests are failing with the following error:
{noformat}
java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: Error received from SDK harness for instruction -1293: org.apache.beam.sdk.util.UserCodeException: java.lang.IllegalStateException: java.lang.ClassCastException: [B cannot be cast to java.lang.String at org.apache.beam.sdk.coders.StringUtf8Coder.encode(StringUtf8Coder.java:37) at org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.encodeAndConcat(RegisterAndProcessBundleOperation.java:607) at org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.handleMultimapSideInput(RegisterAndProcessBundleOperation.java:474) at org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.delegateByStateKeyType(RegisterAndProcessBundleOperation.java:380) at org.apache.beam.runners.fnexecution.state.GrpcStateService$Inbound.onNext(GrpcStateService.java:130) at org.apache.beam.runners.fnexecution.state.GrpcStateService$Inbound.onNext(GrpcStateService.java:118) at org.apache.beam.vendor.grpc.v1p13p1.io.grpc.stub.ServerCalls$StreamingServerCallHandler$StreamingServerCallListener.onMessage(ServerCalls.java:248) at org.apache.beam.vendor.grpc.v1p13p1.io.grpc.ForwardingServerCallListener.onMessage(ForwardingServerCallListener.java:33) at org.apache.beam.vendor.grpc.v1p13p1.io.grpc.Contexts$ContextualizedServerCallListener.onMessage(Contexts.java:76) at org.apache.beam.vendor.grpc.v1p13p1.io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.messagesAvailable(ServerCallImpl.java:263) at org.apache.beam.vendor.grpc.v1p13p1.io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1MessagesAvailable.runInContext(ServerImpl.java:683) at org.apache.beam.vendor.grpc.v1p13p1.io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) at org.apache.beam.vendor.grpc.v1p13p1.io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
{noformat}
Based on the timing of when these issues popped up, I suspect the error might be due to https://github.com/apache/beam/pull/7316.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)