You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Scott Wegner (JIRA)" <ji...@apache.org> on 2018/05/07 20:27:00 UTC

[jira] [Commented] (BEAM-4253) ParDoTest fails in Dataflow ValidatesRunner suite

    [ https://issues.apache.org/jira/browse/BEAM-4253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466437#comment-16466437 ] 

Scott Wegner commented on BEAM-4253:
------------------------------------

From [Slack conversation|https://the-asf.slack.com/archives/C9H0YNP3P/p1525724676000504], this is due to recent [new DoFn|https://github.com/apache/beam/pull/4989] changes.

> ParDoTest fails in Dataflow ValidatesRunner suite
> -------------------------------------------------
>
>                 Key: BEAM-4253
>                 URL: https://issues.apache.org/jira/browse/BEAM-4253
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Scott Wegner
>            Priority: Minor
>
> The Gradle job is finally tuned for the Jenkin machines such that we can get a reliable signal, and we are seeing ParDoTests consistently failing: https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Gradle/208/
> {{java.lang.AbstractMethodError: org.apache.beam.runners.core.SimpleDoFnRunner$DoFnProcessContext.element(Lorg/apache/beam/sdk/transforms/DoFn;)Ljava/lang/Object;
> 	at org.apache.beam.sdk.transforms.ParDoTest$TestDoFn$DoFnInvoker.invokeProcessElement(Unknown Source)
> 	at org.apache.beam.runners.core.SimpleDoFnRunner.invokeProcessElement(SimpleDoFnRunner.java:177)
> 	at org.apache.beam.runners.core.SimpleDoFnRunner.processElement(SimpleDoFnRunner.java:141)
> 	at com.google.cloud.dataflow.worker.SimpleParDoFn.processElement(SimpleParDoFn.java:323)
> 	at com.google.cloud.dataflow.worker.util.common.worker.ParDoOperation.process(ParDoOperation.java:43)
> 	at com.google.cloud.dataflow.worker.util.common.worker.OutputReceiver.process(OutputReceiver.java:48)
> 	at com.google.cloud.dataflow.worker.util.common.worker.ReadOperation.runReadLoop(ReadOperation.java:200)
> 	at com.google.cloud.dataflow.worker.util.common.worker.ReadOperation.start(ReadOperation.java:158)
> 	at com.google.cloud.dataflow.worker.util.common.worker.MapTaskExecutor.execute(MapTaskExecutor.java:75)
> 	at com.google.cloud.dataflow.worker.BatchDataflowWorker.executeWork(BatchDataflowWorker.java:383)
> 	at com.google.cloud.dataflow.worker.BatchDataflowWorker.doWork(BatchDataflowWorker.java:355)
> 	at com.google.cloud.dataflow.worker.BatchDataflowWorker.getAndPerformWork(BatchDataflowWorker.java:286)
> 	at com.google.cloud.dataflow.worker.DataflowBatchWorkerHarness$WorkerThread.doWork(DataflowBatchWorkerHarness.java:134)
> 	at com.google.cloud.dataflow.worker.DataflowBatchWorkerHarness$WorkerThread.call(DataflowBatchWorkerHarness.java:114)
> 	at com.google.cloud.dataflow.worker.DataflowBatchWorkerHarness$WorkerThread.call(DataflowBatchWorkerHarness.java:101)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	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)}}
> It's unclear when these started failing.



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