DanielLeens commented on PR #12015: URL: https://github.com/apache/seatunnel/pull/12015#issuecomment-5569399709
@luozihen Good question — and yes, this is still the same unrelated Doris-connector flake I called out in my last review, not a new failure. I re-checked the fork run just now (`luozihen/seatunnel` run `33743266792`, head `1730aeef`): the only two non-passing jobs are `doris-connector-it (8, ubuntu-latest)` and `doris-connector-it (11, ubuntu-latest)`, both Testcontainers/Docker networking symptoms against the Doris FE/BE containers, plus `kudu-connector-it` which was `cancelled` (a downstream side-effect of the matrix, not a real failure) and a batch of `updated-modules-integration-test-*` jobs that were `skipped`. Nothing in the JDBC/config modules this PR touches is failing. Since this PR's CI runs inside your own fork, you have direct rerun access without needing me or another maintainer: - UI: open the run page on `luozihen/seatunnel` (Actions tab -> this run -> "Re-run jobs" -> "Re-run failed jobs", top-right). - CLI (with your own GitHub auth, not mine): `gh run rerun 33743266792 --repo luozihen/seatunnel --failed` That reruns only the failed/skipped legs, not the whole matrix, so it should be quick. To be clear: CI hasn't actually re-executed since your last push (the HOCON fix + rebase) — GitHub is just still displaying that same red run from 2026-09-03. A rerun is exactly the right next step here, no further code change needed on your side. If it comes back green (or fails again with the same Doris/Testcontainers signature), ping this thread and I'll do a fresh confirmation pass. -- 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]
