SEZ9 commented on issue #12612: URL: https://github.com/apache/seatunnel/issues/12612#issuecomment-6458954882
Thanks for closing the loop on the rerun rather than leaving it implied, @SEPURI-SAI-KRISHNA. Noted that the #12899 Build is green on `639908b12`, with `all-connectors-it-3` passing on both JDKs (114m46s on 11, 147m48s on 17) and every other job success or skipped. Your read of the earlier red matches mine: both JDKs stopping at exactly the 150m cap on a merge-with-`dev` head, one commit after the same lane finished in 112m on `275efb97b`, is runner variance against the cap, not a test failure. The documentation-only diff on `275efb97b` touches no connector code, so nothing there points back at the `BIGINT` range check. If the lane goes red again with no test named, I agree a rerun is the right response, and I will treat it that way rather than ask you to chase it. On the documentation ask: your table of the `IFNULL` / `COALESCE` signature corrections, the per-section workarounds with the reorder caveat, and the Migration Guide line in both EN and ZH covers everything I asked for, and I will do that second look against `639908b12` specifically, since that is the head you verified. Nothing further is needed from your side right now. #12899 is MERGEABLE against `dev` at `c875a87bd` as you re-checked, the Build is green on the reviewed head, and the remaining gate is the write-access review. If anything comes up during that pass I will leave it inline on the PR; please keep `639908b12` as the head in the meantime so the review and the green run stay on the same commit. <!-- streview-comment:2081 --> -- 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]
