DanielLeens commented on PR #11415: URL: https://github.com/apache/seatunnel/pull/11415#issuecomment-5466097746
CI update on the current head (`97e929f7d65a`): the fork's `Build` run (`zhangshenghang/seatunnel` run `33174103702`), which I noted as still `in_progress` in my last review, has since completed with `FAILURE`. The failing job is `unit-test (11, windows-latest)` (`unit-test (8, ubuntu-latest)` and `unit-test (8, windows-latest)` were cancelled as a consequence of that failure, not independent failures). The actual test error is: ``` CheckpointPlanTest > AbstractSeaTunnelServerTest.before:70 » IllegalState Node f... ``` i.e. the embedded Hazelcast instance failing to start while bootstrapping `seatunnel-engine-server`'s unit tests — a module this PR's doc-only commit doesn't touch (the diff is limited to `docs/en` and `docs/zh`'s `incompatible-changes.md`). This is a known environmental flake pattern on `windows-latest` runners (Hazelcast node bootstrap failing intermittently, a different test class each occurrence), not something tied to this PR's format-serialization fix. Recommend a job-level rerun of just `unit-test (11, windows-latest)`; no source-side action needed on this PR — my "Ready to merge" conclusion from my last review stands. -- 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]
