You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2020/10/02 16:07:00 UTC
[jira] [Commented] (BEAM-10472) Failure / flake in direct runner
ParDoLifecycleTest > testTeardownCalledAfterExceptionInFinishBundleStateful
[ https://issues.apache.org/jira/browse/BEAM-10472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206299#comment-17206299 ]
Kenneth Knowles commented on BEAM-10472:
----------------------------------------
https://ci-beam.apache.org/job/beam_PreCommit_Java_Phrase/2761/
> Failure / flake in direct runner ParDoLifecycleTest > testTeardownCalledAfterExceptionInFinishBundleStateful
> ------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-10472
> URL: https://issues.apache.org/jira/browse/BEAM-10472
> Project: Beam
> Issue Type: Bug
> Components: runner-direct
> Reporter: Kenneth Knowles
> Priority: P1
> Labels: flake
>
> https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/12328/testReport/junit/org.apache.beam.sdk.transforms/ParDoLifecycleTest/testTeardownCalledAfterExceptionInFinishBundleStateful/
> {code}
> Expected: is <TEARDOWN>
> but: was <START_BUNDLE>
> {code}
> I don't know if there is non-determinism between shutting down processing and tearing down DoFns, but the DirectRunner should not have this variety of failure, even though production runners may be unable to call teardown.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)