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

   ## What is the purpose of the change
   
   Backport to `release-2.3` of four test-stabilization fixes for 
`RescaleTimelineITCase`, cherry-picked in master-chronological order:
   
   - `[FLINK-40009]` Enforce timeout in the `RescaleTimelineITCase` wait helper 
(master commit `1268adfdb03`)
   - `[FLINK-40010]` Fix race in 
`testRescaleTerminatedByNoResourcesOrNoParallelismsChange` (master commit 
`ad2dee480a6`)
   - `[FLINK-40076]` Fix race in 
`testRecordNonTerminatedRescaleMergingWithNewRecoverableFailureTriggerCause` 
(master commit `7f770b87178`)
   - `[FLINK-40067]` Fix race in `testRescaleTerminatedByJobFinished` (master 
commit `edba4901475`)
   
   `RescaleTimelineITCase` exists only on `release-2.3` (not 2.2/2.1/2.0/1.20), 
and its siblings FLINK-39902 (#28413) and FLINK-39903 (#28414) were already 
backported here, so these fixes close the remaining parity gap. Without 
FLINK-40009 in particular, the same race surfaces as a watchdog hang on 2.3 
rather than a clean `TimeoutException`. Bundled into a single PR because all 
four touch the same file.
   
   ## Brief change log
   
   - Cherry-picked the four commits above (`-x`), each preserving its original 
`[FLINK-xxxxx][tests]` message. The resulting `RescaleTimelineITCase.java` is 
byte-identical to master's.
   
   ## Verifying this change
   
   This change is a test-only stabilization backport and is covered by existing 
tests:
   
   - `RescaleTimelineITCase`
   - `flink-runtime` `test-compile` passes on `release-2.3`.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **no**
     - The public API: **no**
     - The serializers: **no**
     - The runtime per-record code paths (performance sensitive): **no**
     - Anything that affects deployment or recovery: **no**
     - The S3 file system connector: **no**
   
   ## Documentation
   
     - Does this pull request introduce a new feature? **no**
     - If yes, how is the feature documented? **not applicable**
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Opus 4.8 (1M context)
   


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