Rangsh commented on PR #12218: URL: https://github.com/apache/seatunnel/pull/12218#issuecomment-6169297551
Thanks @DanielLeens. I checked the finished fork run for head `35f5a2fcf` (https://github.com/Rangsh/seatunnel/actions/runs/38496659794): 79 jobs green, 13 skipped, 2 failed. I cannot rerun a single failed job from the fork (`gh run rerun --failed` returns "run ... cannot be rerun"), so I read both failure logs instead. 1. `engine-v2-it (11)` (https://github.com/Rangsh/seatunnel/actions/runs/38496659794/job/115650597710) is still exactly the one you identified: `SplitClusterFaultToleranceIT.testStreamJobCancelResolvesWhenWorkerCrashesBeforeCancelAck`, `expected: <CANCELED> but was: <FAILED>`. It does not go through a failed `deployLocalTask`, and the fix (#12311) is still not on `dev`, so I am treating it as the known unrelated cancel-vs-worker-loss race. 2. One job was still running when you reviewed and has since failed: `kafka-connector-it (17)` (https://github.com/Rangsh/seatunnel/actions/runs/38496659794/job/115650597797). The only error is `KafkaIT.testNativeSinkKafka`, and it is not an assertion failure. The same test passed for the other engine parameters in that job; the one error is `ParameterResolutionException: Could not build image: received unexpected HTTP status: 500 Internal Server Error` from the Testcontainers image build. This PR does not touch Kafka or any container image, so I believe this is a runner/registry flake rather than a result of this change. No source change from this round. Happy to paste more of either log if it would help, and thank you again for staying with this. -- 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]
