DanielLeens commented on PR #11959: URL: https://github.com/apache/seatunnel/pull/11959#issuecomment-5423995811
Thanks @davidzollo for the +1! I dug into the current `Build` failure at head `45aa3de8` to confirm it's not related to this diff. The fork run (https://github.com/hiSandog/seatunnel/actions/runs/32823305965) has exactly three non-infra-skip failing jobs: `kudu-connector-it (8, ubuntu-latest)`, `all-connectors-it-2 (8, ubuntu-latest)`, and `rocketmq-connector-it (11, ubuntu-latest)`. I checked the `kudu-connector-it` log directly — it fails before any test code runs, at the Maven Wrapper download step: ``` HTTP request sent, awaiting response... 429 Too Many Requests Error: Could not find or load main class org.apache.maven.wrapper.MavenWrapperMain ``` That's a `repo.maven.apache.org` rate-limit hit during `./mvnw` bootstrap, nothing to do with the Kudu/RocketMQ connector modules or with `seatunnel-common`'s `DryRunConnectFailureMessageSanitizer` that this PR touches. So this looks like a transient CI infra flake rather than a real regression from this change. @hiSandog since there's no new commit needed here, could you push an empty commit or ask a maintainer to re-run the failed jobs (`kudu-connector-it`, `all-connectors-it-2`, `rocketmq-connector-it`) on the fork? Once those come back green this should be ready to merge per davidzollo's conditional +1. -- 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]
