CryoThrust commented on PR #12149: URL: https://github.com/apache/seatunnel/pull/12149#issuecomment-5677230610
A note on the failing `Build` check, in case it shows up in review. It is not this change. Every unit-test job passes; the failures are the connector-v2, transform-v2, rocketmq and engine-v2 integration suites, several of which touch no code this branch goes near (the branch changes only `CheckpointCoordinator.java` and its test). The same `Build` failure appears on my other open seatunnel PRs (#12149, #12101, #12051), which change different files, and on at least one unrelated contributor's PR (#12315) — while pushes to `dev` build green. That points at a fork-side/infrastructure problem rather than the diff. Locally the affected area is green: ``` CheckpointCoordinatorTest 16 run, 0 failures ``` If the check stays red when it is reviewed, `-DskipIT=true` on the relevant suite would confirm the same result, but I did not want to push an empty commit purely to re-trigger CI without asking. -- 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]
