li3zhi4 commented on PR #11746: URL: https://github.com/apache/seatunnel/pull/11746#issuecomment-5450247119
An update on the remaining CI blocker — after **6 reruns** on the same head (`2debe857f`), the two integration shards that have never gone green are consistently hitting **environment/infra issues, not code**: **Failure matrix across the 6 attempts** (`li3zhi4/seatunnel` run `32099067143`): | job | A1 | A2 | A3 | A4 | A5 | A6 | |---|---|---|---|---|---|---| | integration-test-part-2 (11) | fail (image 404) | fail (Spark) | cancelled | fail (ContainerLaunch) | fail (ContainerLaunch) | fail (ContainerLaunch) | | integration-test-part-2 (8) | cancelled | cancelled | fail | cancelled | cancelled | cancelled | - **`JdbcOracleSplitIT`** (part-2 (11)): every failure is the Testcontainers Oracle container (`gvenzl/oracle-xe:21-slim-faststart`) failing to start — latest runs end with `JdbcOracleSplitIT » Completion ContainerLaunchException`, `Tests run: 210, Failures: 0, Errors: 1, Skipped: 1` (only the container launch error; all 209 other tests in the shard pass). This is the same infra flake @DanielLeens identified in the review — the same test passes locally (2/2, container starts fine). - **`JdbcMysqlSplitIT`** (part-2 (8), containing the new STRING-column composite test): has been **cancelled as a cascade every single time** (shard-partner failure) — it is not failing, it just never gets to run. Locally everything the reviewer asked for is verified: the new `testCompositeKeyWithStringColumn` passes 1/1, existing composite tests pass (MySQL 2/2, Oracle 2/2, SQLite 1/1). Since the reviewer confirmed these are runner/network flakes with no code change expected, and CI cannot go green on this head through reruns (failure source differs every attempt), could a maintainer please either trigger a fresh run on their side or advise how to proceed with the known-infra-flake exemption? Happy to provide the full job logs if useful. -- 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]
