DanielLeens commented on PR #11564: URL: https://github.com/apache/seatunnel/pull/11564#issuecomment-5462271930
Follow-up with a more concrete next step than "just rerun." I re-diagnosed the current failing `Build` run (`e01712f9`, same 4 jobs as before: `unit-test (11, windows-latest)`, `engine-v2-it (8, ubuntu-latest)`, `all-connectors-it-7 (11, ubuntu-latest)`, `doris-connector-it (8, ubuntu-latest)`) and looked specifically at `engine-v2-it`'s single failure: `SinkErrorToMysqlIT.testSinkMaxErrorRatioThreshold:615 ยป ConditionTimeout`. That test class had a real flakiness fix land in `dev` the day after this PR's head was pushed: `73e46e0d627` / #11904 (`[Improve][E2E] Use DependencyJar for MySQL error tests`, 2026-08-20). It replaces a network `curl` download of the MySQL driver jar inside the test container with a local `DependencyJar.of(Driver.class).copyTo(...)` copy โ removing exactly the kind of network-timing variance that produces `ConditionTimeout` failures in container-setup-sensitive E2E tests. This PR's head (`e01712f9`, 2026-08-19) predates that fix, and this branch is currently `behind_by=83` commits against `dev` (compare status: `diverged`). So a plain "rerun the failed jobs" on the current head will very likely reproduce the same flake again, since the underlying test code hasn't changed. The lower-cost path is to sync this branch with the latest `dev` first (picking up #11904) and then rerun โ none of the 4 failing jobs touch `ReportMetricsOperation`/`ReportMetricsOperationTest`, so I'd expect a clean run once the sync happens. No new source-side finding from me โ my 08-04 review conclusion still stands unchanged. -- 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]
