DanielLeens opened a new pull request, #12445: URL: https://github.com/apache/seatunnel/pull/12445
### Purpose of this pull request Two integration-test jobs are now cancelled by their own `timeout-minutes` on PRs that do not touch the modules they run, and on `dev` push builds: | job | budget | green duration | cancelled at exactly the budget on | | --- | --- | --- | --- | | `jdbc-connectors-it-part-1` | 120 min | 113-115 min (`dev` runs 35625308814 JDK 11: 1h53m, 35567482965 JDK 8: 1h55m) | #12290, #12182, #12165, #12403, #12420, #12014, #11856, #11496 (fork runs, both JDK legs, 2026-09-19..22); `dev` run 35679211351 both legs, 35625308814 JDK 8, 35567482965 JDK 11 | | `transform-v2-it-part-2` | 150 min | ~149 min (`dev` run 35625308814: 2h29m and 2h28m) | #12182, #12165, #12403 and others; `dev` run 35679211351 both legs, 35567482965 JDK 8 | The cancelled `jdbc-connectors-it-part-1` log of #12420 (JDK 8) shows what is being killed: tests start at 11:34, thirteen classes finish by 13:27 (`JdbcSinkBatchIntervalIT` 19 min, `JdbcOracleIT` 25 min, `JdbcMysqlIT` 22 min, ...) with no failures, and `JdbcDb2UpsertIT` is starting when the runner cancels the job at 13:29, 120 minutes after it began. Nothing hangs; the job has simply grown past its budget, and ordinary runner variance decides whether a given leg finishes. ### Fix (workflow-only) Raise `jdbc-connectors-it-part-1` to 150 minutes and `transform-v2-it-part-2` to 180 minutes, the same headroom the all-modules unit-test job received in #12374 for the same reason. No module is dropped or re-split; #9976 proposes a broader re-split of long-running modules and does not change these two budgets. ### Files - `.github/workflows/backend.yml` ### How was this patch tested? Workflow-only change; the new budgets take effect on this PR's own fork CI and on `dev` once merged. Local checks were limited to a YAML read-back; no local build was run per this initiative's policy. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
