tomatotomata commented on PR #11602: URL: https://github.com/apache/seatunnel/pull/11602#issuecomment-5635723503
Rebased the branch onto the current `apache/seatunnel:dev` at `6ee0c3744` and force-pushed the refreshed head `bc6aefe09`. `spotless:apply` passes on JDK 17 and `git diff --check` passes. The focused `JobMasterTest` run stops during `seatunnel-config-shade` compilation because the shaded Config API types are unresolved before the target test is reached. The fresh GitHub workflow is now running on the rebased head. I was thinking this was the cleanest way to separate the branch-age issue from the remaining CI signal. Let me know what you think. -- 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]
