SEPURI-SAI-KRISHNA commented on PR #12568: URL: https://github.com/apache/seatunnel/pull/12568#issuecomment-6193986886
Status on this PR, since the red `Build` is the only thing left and it is not coming from this change. **The failing lane is `engine-v2-it (11, ubuntu-latest)`, twice.** On the 10-07 run I read the log: the single failure was `BackpressureSlowSinkIT.testCheckpointsKeepCompletingUnderSustainedBackpressure` (1 test run, 1 failure). Today's rerun failed the same lane. I have **not** confirmed that today's failure is the same test method, because the GitHub Actions jobs API is returning HTTP 502 for my fork and I cannot fetch the job log; the lane name is all I have. A third rerun is in flight. **Why this change cannot reach that test**, checked rather than assumed: - The diff is 3 files, all in `seatunnel-api`: `SinkConnectorCommonOptions`, `MultiTableSink`, and `MultiTableSinkWriterTest`. - `BackpressureSlowSinkIT` lives in `seatunnel-e2e/seatunnel-engine-e2e/connector-seatunnel-e2e-base`. - `multi_table_sink_replica` does not appear anywhere under `seatunnel-e2e/seatunnel-engine-e2e`. Zero occurrences. - Every configured value of that option in the repository is `2`, which is above the new lower bound, so no existing config becomes invalid. So the new validation is unreachable from that test. **The flake itself is already tracked, and a fix is already open.** `BackpressureSlowSinkIT` is #12313, and @DanielLeens has #12316 open as the fix (`[Fix][Zeta] Hand the source checkpoint lock to barrier injectors instead of racing them`, created 2026-09-15, currently `mergeable`). The test file has not changed on `dev` since `98ff97a74` added it on 2026-09-10, so syncing `dev` into this branch would not help; I have deliberately not done that, also because a new head could dismiss the existing approval. I am not asking for an exception to the green-CI norm. Two questions for whoever picks this up: 1. Is a further rerun the preferred route here, or is there a better way to get this lane green while #12313 is open? 2. Would merging #12316 be in scope soon? It would clear this lane for every PR that touches it, not only this one. Happy to keep rerunning in the meantime. -- 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]
