Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
None
Description
ParDoLifecycleTest implements tests to assert that DoFn are tore down after another lifecycle method throw an exception.
The implementation uses a static AtomicBoolean for assertions [1]. Unfortunately, this is never reset which results in that boolean being true after the first test which happens to correctly call teardown on exception. Failures for tests executed after are essentially hidden.
This can be seen e.g. by
./gradlew -p runners/spark/ validatesRunnerBatch --tests org.apache.beam.sdk.transforms.ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundle
Attachments
Issue Links
- causes
-
BEAM-7275 ParDoLifecycleTest flaky on SparkValidatesRunner
- Resolved
- links to