abdessalems commented on PR #11727: URL: https://github.com/apache/seatunnel/pull/11727#issuecomment-5245888290
@DanielLeens - closing out your Issue 1. You were right that no CI leg had actually reached `seatunnel-engine-server`: I checked all four `unit-test` legs on this head and the module never ran on any of them (the Windows JDK 11 leg stops in `seatunnel-api`, and fail-fast cancelled the other three). Rather than re-run the full 82-job matrix, I ran the module on its own against this exact head, Ubuntu / JDK 8: ``` maven.compiler.target=1.8 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 - TaskDeployStaleContextRaceTest BUILD SUCCESS ``` Run: https://github.com/abdessalems/seatunnel/actions/runs/31430929790 Both Java files there are byte-identical to e9b25d8 (`TaskExecutionService.java` sha256 `c0ae4127...`, `TaskDeployStaleContextRaceTest.java` sha256 `e8661d5c...`); the only difference on that branch is the workflow file used to launch the run. On the rest of that build: the four other failures are all outside this diff's two files - `MultiTableSinkWriterSchemaChangeBroadcastTest` in `seatunnel-api`, `JdbcPrestoIT`, `MysqlCDCWithFlinkSchemaChangeIT`, and a RocketMQ container failure with no test-level error. The `seatunnel-api` one fails identically on the previous head, before this test existed. Filing the follow-up for the underlying race next and will link it here. -- 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]
