davidzollo opened a new pull request, #12128: URL: https://github.com/apache/seatunnel/pull/12128
## What does this PR do? Two container-readiness waits in the JDBC e2e suite are tighter than the images actually behave on shared CI runners: - **`JdbcHanaIT`** waited 5 minutes for `Startup finished!`. HANA creates its tenant database *after* the container process starts, which can exceed five minutes while startup is still progressing normally. Budget raised to 10 minutes (`HANA_STARTUP_TIMEOUT`). - **`JdbcOceanBaseMilvusIT`** waited only for `boot success!`; the OceanBase image also reports readiness as `Connect to observer ok`. The wait now accepts either line. ## Why is this needed? Both hunks were already being carried locally inside unrelated in-flight PRs whose authors hit the same timeouts (#11458 for HANA, #11503 for OceanBase). PR #11757's run `33971820086` hit both again on dev's versions: `JdbcHanaIT` (`Timed out waiting for log output matching '.*Startup finished!.*'`, 347 s) and `JdbcOceanBaseMilvusIT` (`… '.*boot success!.*'`, 323 s), both `ContainerLaunchException`. Landing them on `dev` so every branch stops paying for them. ## Does this PR introduce any user-facing change? No. Test-only. ## How was this patch tested? The two files are byte-identical to the versions already exercised in CI on #11458 and #11503 respectively; no assertion is changed — only container readiness detection. 🤖 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]
