weiqingy commented on PR #28827: URL: https://github.com/apache/flink/pull/28827#issuecomment-5161385489
The one failing check looks unrelated to this PR. **`test_ci core`**: `RescaleTimelineITCase.testRescaleTerminatedByJobCancelled` timed out with `java.util.concurrent.TimeoutException: Condition was not met within 10000 ms` at `RescaleTimelineITCase.java:698`, called from `:325`. The module tally was `Tests run: 405, Failures: 0, Errors: 1, Skipped: 2`, and that single error is what failed the build. [Azure build 77673](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=77673). Why it cannot be this change: the PR touches 5 files, all under `flink-table/flink-table-api-java` and `flink-table/flink-table-planner`, and neither module is in the `core` stage's reactor. `tools/ci/stage.sh` lists no table module in `MODULES_CORE`, and the core stage runs `-pl $MODULES_CORE -am`, which pulls in upstream dependencies only. The stage that does cover these files, `test_ci table`, passed in the same build, as did `compile_ci` and all four e2e legs. The failure also looks like a timing flake rather than a real regression. The test races a rescale, a `cancelJob`, and the scheduler's async history recording, then polls for all of it inside a fixed 10000 ms budget with no latch or barrier. The sibling test 20 lines above already uses 60000 ms for the same kind of wait, with the comment "Generous budget: on a loaded CI leg the unblock-to-finish window can itself exceed 10s". Retriggering CI to confirm. -- 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]
