weiqingy commented on PR #28827: URL: https://github.com/apache/flink/pull/28827#issuecomment-5171244964
Still red on `test_ci core` (module `flink-runtime`), but on a different test than last time. Both legs ran the same tree, since the retrigger commit was empty: - [77673](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=77673): `RescaleTimelineITCase.testRescaleTerminatedByJobCancelled`, `TimeoutException: Condition was not met within 10000 ms` at `RescaleTimelineITCase.java:698` from `:325`. - [77684](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=77684): `DefaultSchedulerTest.testStoppingCheckpointSchedulerAfterExecutionGraphFinished`, `expected: null but was: org.apache.flink.runtime.checkpoint.CheckpointCoordinator@1e6cec20` at `DefaultSchedulerTest.java:761` from `:742`. Module tally `Tests run: 10124, Failures: 1, Errors: 0, Skipped: 381`. Same source tree, two different failures, so this does not look like a regression from this PR. 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. `test_ci table`, the stage that does cover these files, passed in both builds. The clearest evidence is on `master` itself. Build [77188](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=77188) is a scheduled `refs/heads/master` run from 2026-07-17 (`sourceVersion` `80f0587c774`), ten days before this PR was opened, and its `core` log carries the byte-identical signature: ``` Run 1: RescaleTimelineITCase.testRescaleTerminatedByJobCancelled:324 » AssumptionViolated Run 2: ...:325->waitUntilConditionWithTimeout:698 » Timeout Condition was not met within 10000 ms. ``` Same test, same two line numbers, on a commit that does not contain this change. Both failures also occur outside this PR. I grepped the failed `core` legs on the PR and master/release mirrors back to early March: - `RescaleTimelineITCase.testRescaleTerminatedByJobCancelled` fails with the identical two-run signature (run 1 `AssumptionViolated`, run 2 timeout at the same `:325` and `:698`) on master builds [77188](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=77188), [75390](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=75390), [75252](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=75252), [74704](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=74704), on release-2.3 builds [76078](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=76078), [74591](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=74591), and on the unrelated table-only PR #28316 (build [76482](https://dev.azure.com/apache-flink/98463496-1af2-4620- 8eab-a2ecc1a2e6fe/_build/results?buildId=76482)). FLINK-40150 tracks the `assumeTrue` plus cluster-rebuild pattern behind the run-1 skip. - `DefaultSchedulerTest` is a recurring flake at the class level: other methods in it fail on master builds [73422](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=73422), [74617](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=74617), [75618](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=75618), on release-2.3 build [76434](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=76434), and on the unrelated table-only PR #27895 (build [73888](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=73888)). I did not find this specific method failing anywhere else, so I would not call it a known flake yet. The leg runs test classes concurrently under CPU contention, which fits the pattern. One caveat on those counts: only builds whose final result is `failed` can be enumerated, so a leg that failed and was later re-run green is invisible. The occurrences above are a lower bound. For what it is worth, `flink-runtime/pom.xml` has no `flink-table` dependency at all, so there is no code path from this diff to the failing module. -- 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]
