You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Thomas Weise (JIRA)" <ji...@apache.org> on 2016/12/22 01:02:43 UTC
[jira] [Commented] (BEAM-1140) Apex
ParDoBoundTranslatorTest.testMultiOutputParDoWithSideInputs is flaky
[ https://issues.apache.org/jira/browse/BEAM-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768641#comment-15768641 ]
Thomas Weise commented on BEAM-1140:
------------------------------------
Run it for ~ 30 minutes using
{code}
while mvn test -Dtest=ParDoBoundTranslatorTest#testMultiOutputParDoWithSideInputs; do :; done
{code}
without error. But I have seen this failing in a different environment before as well.
> 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)