mengw15 opened a new pull request, #8523:
URL: https://github.com/apache/texera/pull/8523

   ### What changes were proposed in this PR?
   
   `Backport Approvals` is a required status check on `main`, and GitHub 
evaluates the LATEST check run with that name. The workflow's concurrency group 
had `cancel-in-progress: true`, so when two PR events land close together (a 
push right after a review request or a label change), the newer run cancels the 
older one — and when the older run's "cancelled" terminal state is recorded 
after the newer run's success, the required check reads as failed and the merge 
button is blocked. This happened on #8516: the check showed a cancelled run as 
its latest state while a sibling run of the same commit had already passed; 
re-running the cancelled run unblocked the merge.
   
   The job completes in seconds, so cancellation saves nothing. This switches 
the group to queue (`cancel-in-progress: false`): every run completes, the 
latest check run always carries a real conclusion, and queued runs execute in 
event order so the newest evaluation still reports last.
   
   ### Any related issues, documentation, discussions?
   
   Closes #8522. Observed on #8516 (a cancelled `Backport Approvals` run 
blocked an otherwise green merge).
   
   ### How was this PR tested?
   
   Config-only change to the workflow's concurrency setting; no executable code 
path changes. Verified the failure mechanism on #8516: the blocked merge showed 
the cancelled run as the latest `Backport Approvals` check run, and re-running 
it (6s pass) unblocked the merge immediately.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Yes. Generated-by: Claude Code (Claude Fable 5, Anthropic). Reviewed by the 
author before submission.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


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