DanielLeens commented on PR #11844: URL: https://github.com/apache/seatunnel/pull/11844#issuecomment-5390005899
Thanks for the update, @zhang-arvin — and thanks for double-checking the failures rather than just asking me to re-approve blind. I pulled the actual job logs from your fork's run for head `093544fce` (the same commit I already reviewed, so nothing to re-review code-wise): - `updated-modules-integration-test-part-3 (11, ubuntu-latest)`: fails during dependency resolution with `Could not transfer artifact com.fasterxml.jackson.dataformat:jackson-dataformat-properties:jar:2.15.4 ... status: 502 Bad Gateway`. That's Maven Central returning a transient 502, nothing to do with this PR's diff. - `unit-test (11, windows-latest)`: fails with `TaskTest>AbstractSeaTunnelServerTest.before:70 » IllegalState Node failed to start!` — a known Hazelcast-node-startup flake on windows-latest in `seatunnel-engine-server`, unrelated to `connector-cdc-mysql`. So yes, both failures are environmental/infra, exactly as you said — nothing left to fix in this PR. My last review already had no blockers (only a non-blocking doc-wording nitpick from the prior round, which the `093544fce` commit addressed). The remaining step is just getting a clean CI run — a rerun of those two jobs should do it, no further code changes needed on your end. -- 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]
