davidzollo commented on PR #12109: URL: https://github.com/apache/seatunnel/pull/12109#issuecomment-5666013550
With the `ScheduleStrategy.WAIT` fix, `testManyPipelinesRestoreContentionInWorkerDown` now reliably reaches the intended scenario (worker killed under multi-pipeline slot contention), but the job then ends `JobStatus.UNKNOWABLE` after the full 5-minute post-kill budget instead of a terminal state, on both JDK 8 and JDK 11 (CI run 34226272462, on head `40373e75c`). That's the `CoordinatorService` job-scheduling completion chain wedging on the pending-job-schedule-runner -- an engine gap tracked in apache/seatunnel#12202, not a defect in this test. Per your earlier suggestion, marked the test `@Disabled` with a pointer to #12202 in `3a6514e6e2a` so this PR's coverage can land without keeping `engine-v2-it` red. Will re-enable once #12202 is fixed. -- 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]
