SEPURI-SAI-KRISHNA commented on PR #12595:
URL: https://github.com/apache/seatunnel/pull/12595#issuecomment-6184348390
@SEZ9 @DanielLeens the green run you both asked for is in.
`Build` on head `db7c965c1c` is **passing**: run `38523018557`, 94 jobs,
finished 2026-10-15 03:18 UTC. Daniel, thank you for re-verifying that this
head is only a `dev` merge over `364514f12c` and that the patch itself is
unchanged.
It took one failed-jobs rerun, and both reds were outside this PR's files:
1. `all-connectors-it-6 (11)`:
`DatabendCDCSinkIT.testDatabendSinkCDC{TestContainer}[1]`, in
`connector-databend-e2e`. This is the signature named in #12482.
2. `google-pubsub-connector-it (17)`:
`GooglePubSubIT.testGooglePubSubSourceAcknowledgesAfterCheckpoint`,
`java.util.concurrent.TimeoutException` at `GooglePubSubIT.java:228`, in
`connector-google-pubsub-e2e`.
Both passed on the rerun with no code change, which is what you would expect
of a container timing flake rather than a real regression. This PR touches only
`seatunnel-engine-server` and `seatunnel-engine-e2e`, so neither connector
module is reachable from its diff.
The `CassandraIT` failures that were red on the previous head are gone, as
predicted once #12756 (`07d6f2235a`) came in with the `dev` sync.
So the state is: javadoc confirmation given and verified in the pushed
history at `b3f26aeb9`, `dev` synced, CI green, and no review comments
outstanding. The only remaining gate is a committer approval, since the PR
still shows `review-required`.
--
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]
