yihua opened a new issue, #19526: URL: https://github.com/apache/hudi/issues/19526
ASF Infra disabled GitHub Actions on apache/hudi on 2026-08-04 over how much runner time our CI consumes (discussion #19515). Nothing can be verified or merged until we are back inside the [ASF GitHub Actions policy](https://infra.apache.org/github-actions-policy.html), which sets concurrency MUST be at most 20, SHOULD be at most 15, and caps a project at 4,200 runner-hours per week. Measured on master before the trim: 71 checks per push, peak 63 concurrent runners, roughly 46 runner-hours per push. The matrix runs the same suites across Spark 3.3 through 4.2 and Flink 1.18 through 2.1, so a single push pays for every supported version of every engine. The immediate need is to get back within the policy. Cutting Java CI to one configuration per area (a Spark lane on Java 11, a Spark lane on Java 17, a Flink lane, bundle validation, integration tests) brings this to 19 checks, peak around 16, roughly 10 runner-hours per push. This is an interim measure, not a statement about which versions we support. The lanes it takes out should be commented in place rather than deleted so they can be restored as budget allows, and the coverage it drops (Spark 3.3/3.4/4.0/4.1 and Flink 1.18 through 2.0 datasource modules, and the Flink, Kafka Connect and metaserver bundles) has to come back another way. Fixed by #19514. Coverage restoration and the remaining concurrency work are tracked in #19524. -- 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]
