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-1140) Apex ParDoBoundTranslatorTest.testMultiOutputParDoWithSideInputs is flaky
Date Tue, 03 Jan 2017 20:35:58 GMT

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

Thomas Weise commented on BEAM-1140:
------------------------------------

The termination event is a control tuple that follows the data flow. If everything works as
intended, then the topology will be terminated only once the watermark has traversed it fully.
Something isn't working as intended, this workaround reduces the likelihood of the race condition.



> Apex ParDoBoundTranslatorTest.testMultiOutputParDoWithSideInputs is flaky
> -------------------------------------------------------------------------
>
>                 Key: BEAM-1140
>                 URL: https://issues.apache.org/jira/browse/BEAM-1140
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-apex
>            Reporter: Eugene Kirpichov
>            Assignee: Thomas Weise
>
> The test fails about one in 10-20 times or so when run in "Run until failure" mode in
IntelliJ (I did it 3 times; once it failed on the 3rd run, once on the 15th, once on the 40th).
> It's making precommits unstable (e.g. currently https://github.com/apache/incubator-beam/pull/1565
failed with this test error).
> Unfortunately I don't understand enough about the Apex runner to understand what's going
on and fix this myself...



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

Mime
View raw message