[
https://issues.apache.org/jira/browse/BEAM-5814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16672220#comment-16672220
]
Daniel Oliveira commented on BEAM-5814:
---------------------------------------
A very similar flake has occured in the Java PostCommit:
https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1802/testReport/junit/org.apache.beam.runners.dataflow.worker.fn.control/RegisterAndProcessBundleOperationTest/testProcessingBundleHandlesUserStateRequests/
java.util.concurrent.ExecutionException:
org.mockito.exceptions.base.MockitoException:
No argument value was captured!
You might have forgotten to use argument.capture() in verify()...
...or you used capture() in stubbing but stubbed method was not called.
Be aware that it is recommended to use capture() only with verify()
Brief snippets of the stacktrace, in case the link disappears:
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at
java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1895)
at org.apache.beam.sdk.util.MoreFutures.get(MoreFutures.java:57)
at
org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperation.finish(RegisterAndProcessBundleOperation.java:276)
at
org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperationTest.testProcessingBundleHandlesUserStateRequests(RegisterAndProcessBundleOperationTest.java:615)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
...
Caused by: org.mockito.exceptions.base.MockitoException:
...
at
org.apache.beam.runners.dataflow.worker.fn.control.RegisterAndProcessBundleOperationTest$7.lambda$handle$0(RegisterAndProcessBundleOperationTest.java:561)
at
org.apache.beam.sdk.util.MoreFutures.lambda$supplyAsync$0(MoreFutures.java:104)
at
java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)
at
java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1618)
...
> Failure in
> RegisterAndProcessBundleOperationTest.testProcessingBundleHandlesMultimapSideInputRequests
> -----------------------------------------------------------------------------------------------------
>
> Key: BEAM-5814
> URL: https://issues.apache.org/jira/browse/BEAM-5814
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Reporter: Kenneth Knowles
> Assignee: Ankur Goenka
> Priority: Critical
> Labels: flake
>
> https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/1724/
> https://scans.gradle.com/s/xpsswtkdf62so/tests/jpaz6qjpaw4ma-czu63fxt273w6
> {code}
> java.util.concurrent.ExecutionException:
> org.mockito.exceptions.base.MockitoException:
> No argument value was captured!
> You might have forgotten to use argument.capture() in verify()...
> ...or you used capture() in stubbing but stubbed method was not called.
> Be aware that it is recommended to use capture() only with verify()
> ...
> {code}
> Assigning to someone I think has some context as we have no code history or
> blame for the Dataflow Worker. Do with this bug as you see fit. (filing all
> flakes as critical for project health reasons)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
