beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (BEAM-1139) Investigate failures in precommit - Apex & Kryo
Date Tue, 13 Dec 2016 03:18:58 GMT

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

Kenneth Knowles edited comment on BEAM-1139 at 12/13/16 3:18 AM:
-----------------------------------------------------------------

Unfortunately not. Further bummer: the postcommit is not a superset of the precommit so it
never broke. That would provide a much easier trail.


was (Author: kenn):
Unfortunately not. Further bummer: the postcommit does not mirror the precommit so it never
broke. That would provide a much easier trail.

> Investigate 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: Thomas Weise
>            Priority: Minor
>
> 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)

Mime
View raw message