rakeshkodathala opened a new pull request, #29718:
URL: https://github.com/apache/flink/pull/29718

   ## What is the purpose of the change
   
   Backport #29560 to `release-2.4`, as requested in the original review, to 
fix FLINK-34224. Asynchronous upload callbacks in `ChangelogStorageMetricsTest` 
could race with `persist()` when using `SyncMailboxExecutor`.
   
   ## Brief change log
   
   Clean cherry-pick of a7f4db7326a84cc7fbf075c99e2129364e493b0f, with no 
adaptations. Run upload callbacks through the test thread's mailbox and wait 
for upload completion before the next round. Only 
`ChangelogStorageMetricsTest.java` changes.
   
   ## Verifying this change
   
   - All 7 tests in `ChangelogStorageMetricsTest` passed during `./mvnw -B 
clean verify` (Java 17). Full verification failed in `flink-connector-files` 
after the affected `ChangelogStorageMetricsTest` passed all 7 tests. This 
unrelated failure needs review in CI.
   - Passed module Spotless formatting and whitespace checks.
   - Full repository verification is still in progress.
   - The patch matches the merged original fix. The original reviewer 
reproduced the hang on master and confirmed the fix; no separate before/after 
reproduction is claimed for this release branch.
   
   ## Does this pull request potentially affect one of the following parts:
   
   - Dependencies: no.
   - Public API: no.
   - Serializers: no.
   - Runtime per-record code paths: no.
   - Deployment or recovery: no production changes; tests only.
   - S3 file system connector: no.
   
   ## Documentation
   
   - New feature: no.
   - Documentation: not applicable.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Codex (GPT-6) assisted with the backport and validation.
   
   Generated-by: Codex (GPT-6)
   


-- 
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