DanielLeens opened a new pull request, #11845: URL: https://github.com/apache/seatunnel/pull/11845
### Purpose of this pull request Stabilize `CouchbaseIT`, which has been failing `all-connectors-it-1 (8, ubuntu-latest)` since 2026-08-15 across unrelated PR branches, job reruns, and apache/dev push builds (e.g. dev run 32011043377, PR runs 31993137762 attempts 1 and 2, 31792627420), always with the same ~19s signature: ``` ContainerLaunchException: Could not create/start container Caused by: RuntimeException: Could not perform request against couchbase HTTP endpoint Caused by: java.net.SocketException: Connection reset (or: unexpected end of stream) ``` ### Why the existing mitigation does not cover this The connector shipped with `withStartupTimeout(Duration.ofMinutes(3))`, but that budget only governs the wait strategy. The failing REST bootstrap (`renameNode` etc.) runs earlier, inside testcontainers 1.17.6's `containerIsStarting`, has no retry of its own, and aborts the entire start on the first `IOException`. With the default single start attempt, the job dies immediately. ### What this PR changes (test-only, no assertion or timeout changes) - `withStartupAttempts(3)`: retries the whole container start with a fresh server, covering the un-retried `containerIsStarting` window. - `Slf4jLogConsumer` with prefix `couchbase-server`: streams the server's stdout/stderr into the CI job log, so if startup still fails the log shows why the couchbase daemon dropped the connection instead of only the client-side socket error. ### Check list - [x] Test-only change under `seatunnel-e2e`; no production code touched. - [x] `./mvnw spotless:apply -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-couchbase-e2e` run. - [ ] Functional validation via GitHub CI (`all-connectors-it-1` / `updated-modules` shard containing CouchbaseIT). -- 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]
