li3zhi4 commented on PR #11746: URL: https://github.com/apache/seatunnel/pull/11746#issuecomment-5300237684
Just a heads-up on the fork CI status after several reruns — all remaining failures are environment flakiness, not code. **Rerun history** (`li3zhi4/seatunnel` run `31763472433`, 4 attempts): | job | A1 | A2 | A3 | A4 | |---|---|---|---|---| | integration-test-part-2 (11) | fail | cancelled | fail | fail | | integration-test-part-3 (11) | fail (Maven wrapper 403) | fail | cancelled | pass | | unit-test (8, windows) | cancelled | fail | pass | pass | | integration-test-part-2 (8) | — | fail | cancelled | cancelled | | integration-test-part-3 (8) | — | cancelled | fail | pass | | kafka-connector-it (8) | fail | pass | pass | pass | Every job that has ever failed also passed in another attempt — the failure point keeps drifting between runs (Maven wrapper downloads, testcontainer image pulls, windows runner hiccups), which is the signature of runner/network instability rather than anything in this diff. @DanielLeens already confirmed in the latest review that the failing jobs were infra flakes with no code change expected. Code-wise the PR has a clean bill of health (five review rounds, all findings fixed or resolved, single-column-PK path byte-identical). Could a maintainer please take a look at merging once CI settles, or advise if a fresh run on your side is preferred? -- 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]
