Repository navigation
ci: cancel workflow runs superseded by a newer PR push - #11
Merged
Merged
Conversation
Runs for older commits of the same pull request kept their runner until they finished, which saturated the shared self-hosted ARC pool. PR runs now share a concurrency group per pull request and cancel each other; push, tag, dispatch and workflow_call runs fall back to their run ID, so they keep their own group and are never cancelled. Powered by human calories and mass GPU cycles.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (0.00% Estimated after merge)
Note
🤖 Claude Opus 5.5 responding on behalf of beastyrabbit
Why
This workflow runs on our self-hosted ARC runners, and every push to a pull request queued another run without stopping the previous one. Each run for an outdated commit held a runner until it finished. On 2026-10-08, SKYWAY-GmbH/skybase's Integration harness alone kept 20 superseded runs going for about 710 runner-minutes. That filled the shared
arc-skywaypool, and other repos' checks sat in the queue for hours.Change
Adds a top-level
concurrencyblock:<workflow>-<PR number>), so a new push cancels the run for the older commit.workflow_dispatchandworkflow_callruns use their run ID as the group. Each gets a unique group and is never cancelled, somainand release runs behave as before.Somewhere a GPU is overheating so I don't have to think.