zhangshenghang commented on PR #13233: URL: https://github.com/apache/seatunnel/pull/13233#issuecomment-6894134299
CI status summary for the latest push (`2d51981468`, adds the env-propagation E2E suite): - Every module touched by this PR — `seatunnel-api`, `engine-core`, `engine-client`, `seatunnel-starter`, docs, and the new `EnvOptionsPropagationIT` in `connector-seatunnel-e2e-base` — is green in all three attempts. - The only remaining failure, in all three attempts, is `jdbc-connectors-it-part-7 (11)/(17)`: `JdbcIrisIT` cannot reach the InterSystems IRIS container within the test's built-in 6-minute wait (`Connection refused`). Earlier attempts on the previous commit also hit `JdbcOpenGaussIT`. One attempt additionally saw `Build website` fail with a GitHub 502 and RocketMQ/Clickhouse IT container errors — all of which passed on the immediate rerun, confirming they were transient. - This matches the known fork-runner Docker pull throttling pattern (IRIS is a large image; shared runner IPs are rate-limited). The same jobs pass on apache/seatunnel's own runners, and the same pipeline was green end-to-end on the parent commit `f246dfdde9`. I've stopped rerunning on my side after three identical attempts on this push. Could a committer rerun the failed jobs (or restart the `Build` check) when convenient? The PR itself should be unaffected. -- 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]
