Abacn commented on PR #28614:
URL: https://github.com/apache/beam/pull/28614#issuecomment-1830681463

   It appears this change may also caused Flink ValidatesRunner to became 
extremely flaky: 
https://github.com/apache/beam/actions/workflows/beam_PostCommit_Java_ValidatesRunner_Flink.yml?page=6&query=event%3Aschedule
   
   Although this test suite has always been flaky (~30% fail rate), prior to 
Oct 27th it became extremely flaky (<5% success rate)
   
   Some example errors:
   ```
   testAfterProcessingTimeContinuationTriggerUsingState
   
   java.lang.AssertionError: Second Triggered 
sum/Values/Values/Map/ParMultiDo(Anonymous).output: 
   Expected: iterable with items [<42>] in any order
        but: no match for: <84>
   ```
   
   ```
   testTeardownCalledAfterExceptionInStartBundleStateful
   
   java.lang.AssertionError: Expected to have a processing method throw an 
exception
        at org.junit.Assert.fail(Assert.java:89)
        at 
org.apache.beam.sdk.transforms.ParDoLifecycleTest$ExceptionThrowingFn.after(ParDoLifecycleTest.java:460)
   ```
   
   ```
   testTriggeredLatestSingleton
   
   org.apache.beam.sdk.Pipeline$PipelineExecutionException: 
java.lang.IllegalArgumentException: PCollection with more than one element 
accessed as a singleton view.
        at 
org.apache.beam.runners.flink.TestFlinkRunner.run(TestFlinkRunner.java:75)
        at org.apache.beam.sdk.Pipeline.run(Pipeline.java:321)
        at org.apache.beam.sdk.testing.TestPipeline.run(TestPipeline.java:398)
   Caused by: java.lang.IllegalArgumentException: PCollection with more than 
one element accessed as a singleton view.
        at 
org.apache.beam.sdk.values.PCollectionViews$SingletonViewFn2.apply(PCollectionViews.java:412)
        at 
org.apache.beam.sdk.values.PCollectionViews$SingletonViewFn2.apply(PCollectionViews.java:339)
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to