dybyte commented on PR #10595: URL: https://github.com/apache/seatunnel/pull/10595#issuecomment-4060857952
> Hi @dybyte @liunaijie, > > CI has been triggered and I've already re-run the failed jobs multiple times (5 attempts so far). Some previously failing jobs have passed after re-runs, but the following 3 jobs consistently fail across all attempts and appear to be unrelated to the changes in this PR: > > 1. **`all-connectors-it-6 (11, ubuntu-latest)`** — `Process completed with exit code 1` in "run connector-v2 integration test (part-6)". This PR only modifies files in `seatunnel-engine-server` (REST API layer), and the failing job runs connector-v2 e2e integration tests with `-DskipUT=true`, which does not execute any of the tests added/modified in this PR. > 2. **`all-connectors-it-6 (8, ubuntu-latest)`** — Automatically canceled due to the default `fail-fast: true` matrix strategy after the Java 11 variant above failed. > 3. **`Build website`** — `The job has exceeded the maximum execution time of 1h0m0s` during "Run docusaurus build". This is a website build timeout, completely unrelated to the code changes. > > These failures seem to be pre-existing flaky tests / infrastructure issues on the `dev` branch. Could you please help review and advise? Thank you! Could you try re-running the CI with a clean [cache](https://github.com/nzw921rx/seatunnel/actions/caches)? -- 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]
