DanielLeens commented on PR #11307: URL: https://github.com/apache/seatunnel/pull/11307#issuecomment-5466090137
Following up on the completed `Build` run for this exact head (`e4e6ec778b`), since my last review only had it as `IN_PROGRESS`. Fork run: https://github.com/goutamadwant/seatunnel/actions/runs/32919343038 completed with `failure`, but the two failing jobs are `all-connectors-it-1 (8, ubuntu-latest)` and `all-connectors-it-1 (11, ubuntu-latest)`, both failing on the same test: `DruidIT.testDruidSink` (`connector-druid-e2e`), an `org.awaitility.core.ConditionTimeoutException` after ~700s waiting for the Druid sink to ingest data. This is not related to this PR's diff -- `connector-druid-e2e` isn't touched anywhere in this PR (all 35 changed files are under the Spark 3.5 starter modules, the Hudi/Iceberg E2E test files, dist/packaging, and docs). For context, `IcebergSourceIT` -- the module I was specifically watching given the earlier Guava/`NoSuchMethodError` concern -- passed cleanly on both JDK 8 and JDK 11 in this same run, so that earlier concern is resolved on this head. The branch is currently `diverged` from `dev` (`ahead_by=48`, `behind_by=75`), which is expected drift over a long review cycle, not evidence of a problem in this PR's own commits. Lowest-cost next step: re-run the two failed `all-connectors-it-1` jobs (I wouldn't expect `DruidIT.testDruidSink` to be caused by anything in this diff, so a clean rerun on the same head is worth trying first); syncing with the latest `dev` is the fallback if the flake doesn't clear on rerun. -- 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]
