DanielLeens commented on PR #11142: URL: https://github.com/apache/seatunnel/pull/11142#issuecomment-5386283119
Checked the failing `Build` check on the current head (`b53f6b3d1b`) directly against the fork's Actions run — both failing jobs are environmental, unrelated to this PR's EXTRACT epoch/subsecond fix: 1. **`unit-test (8, windows-latest)`** — failed before any test ran. The job's own setup step hit `Exception calling "DownloadFile": The remote server returned an error: (403) Forbidden` while fetching the Maven wrapper jar, so it never got past `Could not find or load main class org.apache.maven.wrapper.MavenWrapperMain`. Pure transient network failure on GitHub's runner, nothing to do with this diff. 2. **`all-connectors-it-7 (8, ubuntu-latest)`** — build reached the tests and failed on exactly one: `PostgresCDCIT.testPostgresCdcSnapshotOnlyAndCommittedOffsetStartupModes` (`org.awaitility.core.ConditionTimeoutException`, PostgresCDCIT.java:603). This is a Postgres CDC savepoint/restart test in a completely different module from Transform-V2 — it isn't reachable from this PR's diff at all. For context: there's an open fix for this exact flaky test elsewhere in the queue right now (Postgres-CDC committed-offset recovery after savepoint), so this class of flake should stop showing up once that lands. I don't have push access to this fork (confirmed — `gh run rerun` was rejected with "Must have admin rights to Repository"), so I can't retrigger the failed jobs myself. Given the history here already includes a couple of maintainer-side replacement-PR attempts that ended up adding more confusion than they resolved, I'd rather not go down that road again. @fallintoplace — could you re-run just the two failed jobs from your fork's Actions tab (or push an empty commit / use "Re-run failed jobs")? No code changes needed. Once that's green, from my side this is ready to merge — my last full review found no open code blockers on the current head. -- 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]
