MartijnVisser opened a new pull request, #28378:
URL: https://github.com/apache/flink/pull/28378
## What is the purpose of the change
`RescaleTimelineITCase.testRescaleTerminatedByJobFinished` is flaky on slow
CI. The test requests an upscale to a parallelism that exceeds the available
slots, so the rescale never changes the running parallelism and is only
observable as a recorded history entry. It then unblocks the no-op task
immediately, racing the scheduler recording that second rescale: on a slow
machine the job finishes before the rescale is recorded, the history stays at
size 1, and the size-2 wait times out.
## Brief change log
- Wait until the second rescale has been recorded (history size 2) before
unblocking the task, so the in-progress rescale resolves to `JOB_FINISHED` once
the job finishes.
- Move the `assumeThat(enabledRescaleHistory(...))` skip ahead of the
requirement update so the disabled-history variant skips cleanly.
## Verifying this change
Existing assertions are unchanged; the fix only enforces the ordering the
sibling tests already get. Verified by running
`testRescaleTerminatedByJobFinished` repeatedly in a loop locally without
failure.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: 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 (Claude Opus 4.8 (1M context))
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]
