SEZ9 commented on PR #12454: URL: https://github.com/apache/seatunnel/pull/12454#issuecomment-5853358037
@DanielLeens I followed up on the PostgreSQL CI-completeness item in review `5328947038`. The final logs now establish why that test could not finish on `addd4a621854`: both full-run part-7 jobs stopped in `connector-file-s3-e2e` before reaching PostgreSQL. - [Java 11, job 108537497755](https://github.com/SEZ9/seatunnel/actions/runs/36285303193/job/108537497755): both S3 startup errors repeatedly report Docker `Status 500` / `unauthorized` while pulling `quay.io/minio/minio:RELEASE.2024-06-13T22-53-53Z`; the reactor then explicitly reports `SeaTunnel : E2E : Connector V2 : CDC Postgres ...... SKIPPED`. - [Java 8, job 108537497720](https://github.com/SEZ9/seatunnel/actions/runs/36285303193/job/108537497720) has the same sequence. The S3 module reports 11 tests, 0 failures, 2 startup errors and 2 existing skips on each JVM. These are not PostgreSQL test results. The MinIO image replacement is already merged into `dev@025d08f9bcb0`, so I rebased the same two commits onto that base to allow the PostgreSQL shard to reach the requested test. The new head is `4f86cb0ac63e`. Both commits are `=` in `git range-diff`: no repair to the reviewed runtime logic, fixture logic or assertions was added. The separate OceanBase fix in #12489 is still unmerged and is not included here. On this exact new tree, OpenJDK 11 Spotless and full-reactor `-DskipTests verify` passed, followed by 77 targeted engine/PostgreSQL/PayPal unit tests with 0 failures, 0 errors and 0 skips. [The fresh Build run](https://github.com/SEZ9/seatunnel/actions/runs/36299863061) is now under monitoring. I will report the actual extended `PostgresCDCIT` result when it executes; the old skipped module and local unit tests are not being presented as that evidence. One additional result from the superseded run: its Java 8 engine job hit the existing 150-minute timeout during `testBatchJobCompletesAfterMasterFailoverDuringCloseHandshake`. I ran that unchanged existing case separately on the same `addd4a621854` source with local Java 8 and two CPUs; it passed (1 test, 0 failures/errors/skips). The remote timeout remains recorded and the new-head engine CI still needs to complete. -- 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]
