Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-10472

Failure / flake in direct runner ParDoLifecycleTest > testTeardownCalledAfterExceptionInFinishBundleStateful

    XMLWordPrintableJSON

Details

    Description

      https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/12328/testReport/junit/org.apache.beam.sdk.transforms/ParDoLifecycleTest/testTeardownCalledAfterExceptionInFinishBundleStateful/

      Expected: is <TEARDOWN>
     but: was <START_BUNDLE>

      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.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. BEAM-7752 Java Validates DirectRunner: testTeardownCalledAfterExceptionInFinishBundleStateful flaky

          • P1 - Critical bug: data loss, total loss of function, or loss of testing signal due to test failures or flakiness
          • Open

          Activity

            People

              Unassigned Unassigned
              kenn Kenneth Knowles
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: