Rangsh commented on PR #12081:
URL: https://github.com/apache/seatunnel/pull/12081#issuecomment-7055144328

   **CI update (automated attempts):** I retried fork CI from the author side 
after the earlier note.
   
   - Pushed empty commit `3251e44cb3` (`[Chore][Zeta] Trigger fork Build for 
68b9975dec`) to replay the `push` trigger — no `Build` run was created for 
`68b9975dec` or `3251e44cb3`.
   - `gh workflow run Build` and the REST dispatch API both return **HTTP 422: 
Actions has been disabled for this repository** on `Rangsh/seatunnel` (token 
has `workflow` scope).
   - Repo-level Actions permissions API reports `enabled: true`, so this looks 
like the account/fork **spending-limit or Actions-off** state GitHub describes 
in our `notify_test_workflow` (not something the CLI can override).
   
   **Local tests on this head (same targets as the PR):** 
`IMapFileStorageBatchDeadlineTest`, `IMapFileStorageRingAdmissionTest`, 
`WALDisruptorBoundedAdmissionTest`, and 
`CheckpointManagerTest#testPayloadAndMonitorFailuresStayIsolatedAcrossRestore` 
— all passed on my machine.
   
   Once fork Actions run again, please use [Build workflow → Run 
workflow](https://github.com/Rangsh/seatunnel/actions/workflows/build_main.yml) 
on branch `improve/zeta-checkpoint-state-store-latency-12058` (or re-enable 
Actions on the fork if the UI shows the enable button). I will post the green 
run link on this PR as soon as it exists.


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