DanielLeens opened a new pull request, #10949:
URL: https://github.com/apache/seatunnel/pull/10949
## Why
This PR extracts the remaining actionable CI fixes from the previous CI
follow-up line without mixing them back into the DB2 work.
It addresses two concrete failures observed from the split CI PR line:
1. `engine-v2-it (11)` could fail in `ClusterFailureNoRestoreIT` because the
batch job sometimes finished before the test actually shut down the worker.
2. `all-connectors-it-2 (11)` could lose the hosted runner heartbeat because
the shard was too heavy, especially when `connector-iceberg-e2e` and
`connector-hbase-e2e` ran together with the rest of part-2.
## What is changed
- Stabilize `ClusterFailureNoRestoreIT` by:
- keeping the batch source busy longer with a larger row count per
parallelism
- waiting for the job to reach `RUNNING`
- waiting for observable output progress before shutting down the worker
- Rebalance connector CI shards by:
- removing `connector-iceberg-e2e` and `connector-hbase-e2e` from
`all-connectors-it-2`
- adding a new dedicated `all-connectors-it-8` job for those two heavier
suites
## Validation
Executed in the local checkout used for this PR:
- `./mvnw spotless:apply -nsu -Dmaven.gitcommitid.skip=true -T 3C`
- `git diff --check -- .github/workflows/backend.yml
seatunnel-e2e/seatunnel-engine-e2e/connector-seatunnel-e2e-base/src/test/java/org/apache/seatunnel/engine/e2e/ClusterFailureNoRestoreIT.java`
- Recomputed the workflow split and verified the new layout:
- `all-connectors-it-2`:
`:connector-assert-e2e,:connector-file-cos-e2e,:connector-rabbitmq-e2e,:connector-easysearch-e2e,:connector-qdrant-e2e,:connector-aerospike-e2e`
- `all-connectors-it-8`: `:connector-iceberg-e2e,:connector-hbase-e2e`
## Not fully revalidated in this run
I also attempted a focused local runtime validation for
`ClusterFailureNoRestoreIT`, but the module is currently blocked by an
unrelated upstream compile issue in `LocalModeIT`
(`SeaTunnelClient#getHealthMetrics(String)` is missing from the current API
surface in this branch line). That issue is outside the scope of this PR, so
this PR keeps the fix focused on the two current actionable CI failures only.
--
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]