DanielLeens commented on PR #12129: URL: https://github.com/apache/seatunnel/pull/12129#issuecomment-6313631519
Thanks @SEZ9 and @akshar27. I ran the current head `6d196d4c920` on my fork (https://github.com/DanielLeens/seatunnel/actions/runs/39382715814) so we do not have to wait for the Build check on yours, and here is what it shows. - `JobStatusTest` (the pinning test from this PR) ran in the `unit-test` job and passed: `Tests run: 2, Failures: 0, Errors: 0`. - The `unit-test` jobs are still red, but for an unrelated reason. The only failure in the module run is `LLMBooleanOutputTest.readsLegacyFactoryWrapperWithValidationDisabled` in `seatunnel-transforms-v2` (`InvalidClassException: AbstractMultiCatalogTransform; local class incompatible, stream classdesc serialVersionUID = 7090258061839605137, local class serialVersionUID = -3241928148724104003`). That test was added by #12194 and this PR does not touch `seatunnel-transforms-v2`; the diff here is only `PhysicalPlan.java` and `JobStatusTest.java`. - Other red jobs in that run (`transform-v2-it-part-2`, `mysql-cdc-connector-it`) are also in modules outside this change. So for this PR the relevant signal (`JobStatusTest` green on the current head) is in place, and the remaining red jobs are baseline failures that should be tracked separately rather than fixed here. @akshar27, starting a `Build` run from the Actions tab on your fork is still worthwhile so the apache check attaches to this head, but there is nothing to change in the code. My approval on this PR stands. -- 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]
