You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by li...@apache.org on 2026/08/24 07:12:55 UTC
(seatunnel) branch fix-ci-uniform-updated-modules-it-timeout created (now dccfc75c68)
This is an automated email from the ASF dual-hosted git repository.
davidzollo pushed a change to branch fix-ci-uniform-updated-modules-it-timeout
in repository https://gitbox.apache.org/repos/asf/seatunnel.git
at dccfc75c68 [Fix][CI] Use a uniform 300-minute timeout for updated-modules IT parts
This branch includes the following new commits:
new dccfc75c68 [Fix][CI] Use a uniform 300-minute timeout for updated-modules IT parts
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(seatunnel) 01/01: [Fix][CI] Use a uniform 300-minute timeout for updated-modules IT parts
Posted by li...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davidzollo pushed a commit to branch fix-ci-uniform-updated-modules-it-timeout
in repository https://gitbox.apache.org/repos/asf/seatunnel.git
commit dccfc75c6805b261d682f2468aa45aa0b160609b
Author: David Zollo <da...@gmail.com>
AuthorDate: Mon Aug 24 03:12:34 2026 -0400
[Fix][CI] Use a uniform 300-minute timeout for updated-modules IT parts
The updated-modules split is round-robin by module index, so bucket
contents rotate whenever any e2e module is added or removed. The
per-part tuned timeouts (180/180/300/200/180/210/210/210) therefore go
stale: on PR #11929 (a connector-common change that fans out to the
full e2e matrix) part-5 received jdbc-part-2, clickhouse, file-s3,
cdc-mongodb, hbase, easysearch, sls, aerospike and starter-e2e, and
timed out at 180 minutes on both JDKs in two consecutive attempts with
measured module times of clickhouse 60m, cdc-mongodb 27m and hbase 85m
still unfinished at cancellation. Aligning every part to the 300-minute
budget that part-3 already uses removes the per-bucket tuning fragility
without reducing any test coverage.
---
.github/workflows/backend.yml | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/.github/workflows/backend.yml b/.github/workflows/backend.yml
index 6f6cca79b9..6fbef22b2c 100644
--- a/.github/workflows/backend.yml
+++ b/.github/workflows/backend.yml
@@ -566,7 +566,7 @@ jobs:
matrix:
java: [ '8', '11' ]
os: [ 'ubuntu-latest' ]
- timeout-minutes: 180
+ timeout-minutes: 300
steps:
- uses: actions/checkout@v4
- name: Set up JDK ${{ matrix.java }}
@@ -598,7 +598,7 @@ jobs:
matrix:
java: [ '8', '11' ]
os: [ 'ubuntu-latest' ]
- timeout-minutes: 180
+ timeout-minutes: 300
steps:
- uses: actions/checkout@v4
- name: Set up JDK ${{ matrix.java }}
@@ -662,7 +662,7 @@ jobs:
matrix:
java: [ '8', '11' ]
os: [ 'ubuntu-latest' ]
- timeout-minutes: 200
+ timeout-minutes: 300
steps:
- uses: actions/checkout@v4
- name: Set up JDK ${{ matrix.java }}
@@ -693,7 +693,7 @@ jobs:
matrix:
java: [ '8', '11' ]
os: [ 'ubuntu-latest' ]
- timeout-minutes: 180
+ timeout-minutes: 300
steps:
- uses: actions/checkout@v4
- name: Set up JDK ${{ matrix.java }}
@@ -724,7 +724,7 @@ jobs:
matrix:
java: [ '8', '11' ]
os: [ 'ubuntu-latest' ]
- timeout-minutes: 210
+ timeout-minutes: 300
steps:
- uses: actions/checkout@v4
- name: Set up JDK ${{ matrix.java }}
@@ -755,7 +755,7 @@ jobs:
matrix:
java: [ '8', '11' ]
os: [ 'ubuntu-latest' ]
- timeout-minutes: 210
+ timeout-minutes: 300
steps:
- uses: actions/checkout@v4
- name: Set up JDK ${{ matrix.java }}
@@ -787,7 +787,7 @@ jobs:
matrix:
java: [ '8', '11' ]
os: [ 'ubuntu-latest' ]
- timeout-minutes: 210
+ timeout-minutes: 300
steps:
- uses: actions/checkout@v4
- name: Set up JDK ${{ matrix.java }}