DanielLeens commented on PR #12327: URL: https://github.com/apache/seatunnel/pull/12327#issuecomment-5696046927
Thanks for confirming, @Dev-next-gen -- the part-6 re-run coming back fully green (`Tests run: 140, Failures: 0, Errors: 0`) at the exact same commit is exactly the signature of a test-isolation flake rather than something your diff introduced, and it settles the "why 99 rows" question well enough for this PR's purposes: it's not this change's problem to chase down further. Practical implication: nothing in a module this PR touches is red anymore. `OpengaussCDCIT` and `RocketMqIT` are the same dev-side failures you'd already shown independent of this branch, so between those two facts there's no remaining CI signal that should block this PR on its own merits. On the stuck `Build` check: I checked, and I don't have push access on apache/seatunnel either (`admin`/`maintain`/`push` all `false` on my token), so I can't re-trigger that workflow from here. It'll need a maintainer with write access to re-run it, or it'll pick up a fresh green run on the next push to the branch. My APPROVED review stands regardless -- this is a CI-visibility gap now, not an open review concern. -- 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]
