CryoThrust commented on PR #12152:
URL: https://github.com/apache/seatunnel/pull/12152#issuecomment-6919094364

   The fork workflows are enabled, but the old run could not be recovered: 
after cancelling its stale queued state, GitHub rejected the rerun because it 
was created over a month ago. Dispatching the old branch also returned 422 
because that revision had no `workflow_dispatch` trigger.
   
   I synced current `dev` in `e3679f4d5`, which also brings in the existing 
manual-build entry point. The PR still changes only `CheckpointCoordinator` and 
its test; no new fallback logic or assertion changes were added in this sync.
   
   The complete `CheckpointCoordinatorTest` passes on JDK 11: 20 tests, no 
failures/errors/skips. Scoped Spotless and server-module `-DskipTests verify` 
also pass. As agreed, rejection by both pools remains outside the tested scope.
   
   GitHub created a new 
[Build](https://github.com/CryoThrust/seatunnel/actions/runs/43885011044) on 
the updated head. It is queued, so runner acquisition and the actual CI result 
are still pending; the old infrastructure failure is not being presented as a 
test result.
   


-- 
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]

Reply via email to