beam-commits mailing list archives

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


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:

3530 [15/WriteCounts/Write/WriteBundles:ApexParDoOperator] INFO
 - Opening writer for write operation$TextSink$TextWriteOperation@7947d5f2

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


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

> apex.examples.WordCountTest.testWordCountExample is flaky
> ---------------------------------------------------------
>                 Key: BEAM-1067
>                 URL:
>             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|$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

View raw message