Hi Thomas, This only happens with https://github.com/apache/beam/pull/3356.
Reuven On Mon, Jul 3, 2017 at 6:11 AM, Thomas Weise <t...@apache.org> wrote: > Hi Reuven, > > I'm not able to reproduce the issue locally. I was hoping to see which > thread is attempting to emit the results. In Apex, only the operator thread > can emit the results, any other thread that is launched by the operator > cannot. I'm not aware of ParDo managing separate threads though and assume > this must be a race. If you still have the log, can you send it to me? > > Thanks, > Thomas > > > > On Sat, Jul 1, 2017 at 5:51 AM, Reuven Lax <re...@google.com.invalid> > wrote: > > > pr/3356 fails in the Apex WordCountTest. The failed test is here > > <https://builds.apache.org/job/beam_PreCommit_Java_ > > MavenInstall/12829/org.apache.beam$beam-runners-apex/ > > testReport/org.apache.beam.runners.apex.examples/WordCountTest/ > > testWordCountExample/> > > : > > > > Upon debugging, it looks like this is likely a problem in the Apex runner > > itself. A ParDo calls output(), and that triggers an exception thrown > from > > inside the Apex runner. The Apex runner calls emit on a DefaultOutputPort > > (ApexParDoOperator.java:275), and that throws an exception inside of > > verifyOperatorThread(). > > > > I'm going to ignore this failure for now as it seems unrelated to my PR, > > but does someone want to take a look? > > > > Reuven > > >
