ealeonraz commented on PR #11461: URL: https://github.com/apache/seatunnel/pull/11461#issuecomment-4995705697
@DanielLeens Done on both counts: Actions enabled in the fork, and the branch is rebased onto the latest `dev` (`3656ba8`) — the PR is now a single commit. Refreshed run: https://github.com/ealeonraz/seatunnel/actions/runs/29519036639 Everything is green except the `unit-test` job, which fails in a test unrelated to this PR: `MetricsApiTest.metricsApiTest` in `seatunnel-engine-server` (metrics endpoint returns 500; the log shows `HazelcastInstanceNotActiveException: State: SHUT_DOWN` surfacing through `ExceptionHandlingFilter` — the request hits a stale instance on the hard-coded port 8080). Evidence it's independent of this change: - `seatunnel-engine-server` test scope doesn't include `connector-mqtt` (only connector-fake/console/file-local), so this diff isn't on that test's classpath - The upstream nightly Schedule Backend on clean `dev` at the same commit fails the identical test: https://github.com/apache/seatunnel/actions/runs/29515660951 (`unit-test (11, ubuntu-latest)`) - It failed consistently across JDK 8/11 ubuntu cells in three runs here (Windows cells skip it via `@DisabledOnOs`), including a failed-jobs rerun I didn't touch the engine test in this PR to keep the scope to the connector-mqtt slice, but I'm happy to file a separate issue for `MetricsApiTest` (and take a crack at a fix) if that's useful. -- 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]
