noorall commented on PR #27091: URL: https://github.com/apache/flink/pull/27091#issuecomment-3450792772
From my observation, when this test was introduced, it was only validated on the `DefaultScheduler`, but not on the `AdaptiveScheduler`, which has a different initial job state. In `DefaultScheduler`, a job starts in the `CREATED` state, so the state transition is: `CREATED → RUNNING → ...` In contrast, in `AdaptiveScheduler`, a job starts in the `INITIALIZING` state (see [link](https://github.com/apache/flink/blob/51561476a086fac922b363f07708fba6f78aeed5/flink-runtime/src/main/java/org/apache/flink/runtime/scheduler/adaptive/Created.java#L37 )) resulting in the transition: `INITIALIZING → CREATED → RUNNING → ...` Unfortunately, the flink CI bot that runs during PR submission doesn't verify whether this test passes under `AdaptiveScheduler`—that validation only happens during the daily runs. As the `AdaptiveScheduler` code has been around for a considerable time and this state transition behavior is both intentional and reasonable, I suggest we simply update the test code to fix this issue, without breaking the original assumptions for `DefaultScheduler`. WDYT? @liuml07 @davidradl -- 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]
