You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2016/12/12 22:51:58 UTC

[jira] [Commented] (BEAM-1139) Failures in precommit - Apex & Kryo

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

Kenneth Knowles commented on BEAM-1139:
---------------------------------------

I will see if I can roll forward a trivial fix right now. Grab the ticket back if you like.

> Failures in precommit - Apex & Kryo
> -----------------------------------
>
>                 Key: BEAM-1139
>                 URL: https://issues.apache.org/jira/browse/BEAM-1139
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-apex
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Blocker
>
> https://builds.apache.org/view/Beam/job/beam_PreCommit_Java_MavenInstall/org.apache.beam$beam-examples-java/5775/testReport/junit/org.apache.beam.examples/WordCountIT/testE2EWordCount/
> This is not necessarily a bug in the Apex runner, but it looks like this class cannot be serialized via Kryo while the Apex runner needs it to be. Probably the fix is to roll-forwards a simple change to make it Kryo serializable.
> It is not clear to me the difference between this test run and others. Clearly there is a coverage gap.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)