DanielLeens opened a new pull request, #11138: URL: https://github.com/apache/seatunnel/pull/11138
## What does this PR do? This fixes an unrelated JDBC Db2 E2E startup failure that surfaced while validating PR #11137. The Db2 test was using `ibmcom/db2:latest` and a short startup readiness configuration. On slow runners, the container can spend several minutes in instance initialization before the database is actually usable, which makes the E2E fail for infrastructure timing reasons instead of test logic reasons. ## Changes - pin the Db2 image to `ibmcom/db2:11.5.0.0a`, which matches the Testcontainers validated default instead of relying on `latest` - wait for the official `Setup has completed.` readiness log and extend the startup timeout to 20 minutes for the Db2 test container - keep the change scoped to `JdbcDb2IT` ## Validation - `./mvnw -nsu -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-part-1 spotless:apply` - `./mvnw -nsu -pl seatunnel-e2e/seatunnel-connector-v2-e2e/connector-jdbc-e2e/connector-jdbc-e2e-part-1 -DfailIfNoTests=false -Dtest=JdbcDb2UpsertIT test` Local runtime note: - this machine's Docker Desktop is limited to about 1975 MB RAM, so the Db2 container still did not fully reach the final ready log locally - however, after this change the container progressed well past the previous failure point: it completed instance configuration, ran `DB2START`, and reached `Creating database E2E`, which is materially further than the original startup timeout behavior - `seatunnel-engine-ui` was not changed and was not included in this validation scope -- 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]
