RyanSkraba opened a new pull request, #19:
URL: https://github.com/apache/flink-connector-gcp-pubsub/pull/19

   We sometimes observe the test failure described in FLINK-33018
   
   ```
   Expected :["1", "2", "3"]
   Actual   :["1", "2"]
   ```
   
   This occurs because the thread running the source is explicitly cancelled in 
the **finally** clause.  Unlike the other tests in this class, the source 
thread should run to completion and finish when the last message ID (`"3"`) 
arrives without external intervention.
   
   In rare cases, it was possible for the explicit `cancel()` to happen after 
the two records arrived, but before the third record causes the source to 
cleanly shut itself down and finish.
   
   This is fixed by no longer waiting for any records to arrive, just letting 
the thread run to completion, and _then_ testing the results.
   
   I checked this by running this particular test as a 
`@RepeatedTest(100_000)`.  I have never observed the behaviour described in the 
issue after this change, but I've noticed that *with or without* the change, 
this test will consistently fail after the 16,248-16,250th execution, during 
the `thread.start()`.


-- 
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: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to