beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-1067) apex.examples.WordCountTest.testWordCountExample is flaky
Date Thu, 22 Dec 2016 05:35:58 GMT

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

Thomas Weise commented on BEAM-1067:
------------------------------------

The log is missing the entries for file write, indicating premature termination of the DAG.


On successful run, I see this:

{code}
3530 [15/WriteCounts/Write/WriteBundles:ApexParDoOperator] INFO  org.apache.beam.sdk.io.Write
 - Opening writer for write operation org.apache.beam.sdk.io.TextIO$TextSink$TextWriteOperation@7947d5f2
{code}

To get more information on future CI failure, I would like to enable tuple tracing just for
this test:

{code}
options.setTupleTracingEnabled(true);
{code}

That will hopefully give an indication at which point the pipeline gets terminated.



> apex.examples.WordCountTest.testWordCountExample is flaky
> ---------------------------------------------------------
>
>                 Key: BEAM-1067
>                 URL: https://issues.apache.org/jira/browse/BEAM-1067
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-apex
>            Reporter: Stas Levin
>            Assignee: Thomas Weise
>
> Seems that {{org.apache.beam.runners.apex.examples.WordCountTest.testWordCountExample}}
is flaky.
> For example, [this|https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/5408/org.apache.beam$beam-runners-apex/testReport/org.apache.beam.runners.apex.examples/WordCountTest/testWordCountExample/
] run failed although no changes were made in {{runner-apex}}.



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

Mime
View raw message