DanielLeens commented on PR #12414: URL: https://github.com/apache/seatunnel/pull/12414#issuecomment-5775110474
Thanks for the nudge. I just re-checked live: the head commit is still `fe9d1ef953d` (unchanged) and the `Build` check on that commit is still `failure`, completed at 2026-09-21T04:18:47Z - I don't see a newer run yet, so the rerun hasn't landed on this commit. As noted in my review, the only failing job in that run is `unit-test (8, windows-latest)`, and the failure is `TaskExecutionServiceTest.testStaleTaskDoneCleansOnlyOwnedGenerationResources` in `seatunnel-engine-server`. This PR does not touch any engine code, and that test/class hasn't changed on `dev` since, so it isn't caused by this diff - syncing `dev` alone will not fix it either. Re-running that job has to happen from the fork's own Actions tab (GitHub only lets users with write access to `TianHengZhuang/seatunnel` trigger a rerun there), so @TianHengZhuang, could you click "Re-run failed jobs" on that run? Once it's green (or if it fails again on the same test, which would help confirm this is flaky rather than PR-related), I'll take another look. To be clear, this doesn't change my assessment of the code itself, which I've already approved. -- 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]
