DanielLeens commented on PR #11813: URL: https://github.com/apache/seatunnel/pull/11813#issuecomment-5480642762
CI update on head 3b30b5f6: in my last review I said the fork run was still in progress and too early to call. It has since completed, and the apache-side `Build` check now shows `failure` — but I traced it through to the real fork run (goutamadwant/seatunnel run 33360238023) rather than trusting the label, and the failure is not a code regression from this PR. Breakdown of that run's jobs: all 1096 unit tests pass (0 failures, 0 errors) across every module including `connector-file-base`/`MarkdownReadStrategyTest`, and every integration-test job succeeds. The single failing job, `unit-test (11, ubuntu-latest)`, aborts during the Maven reactor build itself — before any tests in this PR's own module run — with: `[ERROR] Failed to execute goal on project connector-jdbc: ... Failed to read artifact descriptor for org.apache.hive:hive-shims:jar:3.1.3: ... 502 Bad Gateway` That's a transient Maven Central dependency-resolution failure fetching a Hive JDBC transitive for the unrelated `connector-jdbc` module, with nothing to do with Markdown/file-connector code. This looks like rerun-safe CI noise, not a real blocker — worth a rerun before merge purely for a clean CI record, but I wouldn't treat it as a code-side issue. -- 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]
