MartijnVisser opened a new pull request, #299: URL: https://github.com/apache/flink-connector-kafka/pull/299
## What is the purpose of the change Every scheduled weekly run since at least October 2025 has failed, and every run shows the same shape: one Java failure, one Python failure, and ~28 cancelled jobs. Both matrix levels use the GitHub default `fail-fast: true`. The outer `flink_branches` matrix in `weekly.yml` cancels every other branch line ~30 s after the first failing line, and the per-JDK matrix in the shared workflow cancels the sibling JDKs. Because all 30 jobs start within 2 s and a flake surfaces at minute 18-35 of a ~31-minute job, the cancelled jobs have already burned most of their runtime, so fail-fast discards up to 28 of 30 results while saving almost no minutes (example: run [34002024546](https://github.com/apache/flink-connector-kafka/actions/runs/34002024546)). Run [27484280508](https://github.com/apache/flink-connector-kafka/actions/runs/27484280508) shows the Java matrix fully green while only the Python line made the run red. The workflow also starts 30 concurrent jobs, above the [ASF policy](https://infra.apache.org/github-actions-policy.html) of at most 20 per workflow. ## Brief change log - `fail-fast: false` on the outer matrix of `compile_and_test` and `python_test`, so the five branch lines report independently. The per-JDK fail-fast in `flink-connector-shared-utils` is unchanged. - Release lines run a single JDK (17 for the 2.x lines, 11 for the 1.20 line). `main`/2.2-SNAPSHOT keeps 11/17/21 because `push_pr.yml` only covers `main` with 2.2.1. Python runs one JDK per line. 12 concurrent jobs instead of 30, roughly half the runner minutes. None of the failures in the last 14 weekly runs was JDK dependent. - Bump Flink 1.20.4 -> 1.20.5 and 2.1.2 -> 2.1.3. - `timeout_test: 45` for the Java job; green jobs finish in at most ~36 minutes. ## Verifying this change Workflow file only. Validated the YAML (anchor/alias still resolve, 7 Java + 5 Python jobs) and that all six Flink binaries exist on dlcdn. After merge, trigger `workflow_dispatch` on the weekly workflow: every branch line should reach a conclusion and at most 12 jobs run concurrently. ## 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: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01AXDVMvWdbF2NVwikLZhaYX -- 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]
