DanielLeens commented on PR #12578: URL: https://github.com/apache/seatunnel/pull/12578#issuecomment-6383299597
Thanks @hutiefang76 for posting the final result of run 39775915510 and for retrying the JDK 11 unit-test job; its pass confirms that one was the dependency-download network error. On the remaining `engine-v2-it (11, ubuntu-latest)` failure ([job](https://github.com/hutiefang76/seatunnel/actions/runs/39775915510/job/119919175848)), you can save yourself the separate investigation: the timeout waiting for the first completed checkpoint at `BackpressureSlowSinkIT.java:184` is a known `dev`-level issue, not something in this PR. It has also failed on `dev`'s own `engine-v2-it` on both JDK 8 and JDK 11. The cause is in the Zeta source flow: under sustained backpressure, `FakeSourceReader#pollNext` holds the checkpoint lock for a long batch, and `SourceFlowLifeCycle#collect` releases and re-enters it almost immediately, so the barrier injector in `triggerBarrier` can keep losing the unfair monitor race until the checkpoint times out. It is tracked by #12316 (engine fix) and #12313 (test-side fix), and both are still open, so syncing with `dev` will not clear it yet. Nothing in this PR touches the source flow or checkpoint path; it only changes the `SeaTunnelRow` byte-size cache. Minimal next step: rerun only the failed `engine-v2-it (11, ubuntu-latest)` job once more ("Re-run failed jobs"). If it fails again with the same `:184` timeout, link that run and leave it there; no source change, empty commit or test tweak should go into this PR for it. As before, the fork `workflow_dispatch` run is evidence for this exact commit but does not attach as the PR-bound `Build` check, so a maintainer still needs to retry the failed `Notify test workflow` ([job](https://github.com/apache/seatunnel/actions/runs/38787676286/job/116603788523)) to produce the required check. My source-level conclusion is unchanged: no source-side blocker. -- 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]
