Remove the group that has never let the rebase run start #1086

Merged
jaylouisw merged 1 commit from ci/auto-rebase-no-concurrency into main 2026-11-08 15:57:20 +00:00
Owner

Over the entire history of this workflow the database holds fourteen runs: ten cancelled, four waiting, and not one that ever started. started is epoch 0 on every single one — including the push-triggered run created the moment #1083 landed, which was supposed to be the fix.

They all entered concurrency: {group: auto-rebase}. A run that enters a group and never gets a runner blocks every later run in that group: the group drains in order, and the order never advances past the stuck one. cancel-in-progress: true does not rescue it — it cancels running jobs, not waiting ones, so the waiting runs just accumulate behind the one that will never move.

Bringing the two fixes together, #1071 was treating a symptom: the group was the trap, and the first run to fall into it stayed there.

Two rebase passes overlapping is not a correctness problem. Each pass reads mergeable, rebases one branch at a time, and pushes only to pull-request branches; the worst case is a pass finding a branch already current and reporting it as current.

So the group goes. If the run still does not start after this, the problem is not in this file — and that will be worth knowing too.

Over the entire history of this workflow the database holds **fourteen runs: ten cancelled, four waiting, and not one that ever started.** `started` is epoch 0 on every single one — including the push-triggered run created the moment #1083 landed, which was supposed to be the fix. They all entered `concurrency: {group: auto-rebase}`. A run that enters a group and never gets a runner blocks every later run in that group: the group drains in order, and the order never advances past the stuck one. `cancel-in-progress: true` does not rescue it — it cancels *running* jobs, not *waiting* ones, so the waiting runs just accumulate behind the one that will never move. Bringing the two fixes together, #1071 was treating a symptom: the group was the trap, and the first run to fall into it stayed there. Two rebase passes overlapping is not a correctness problem. Each pass reads `mergeable`, rebases one branch at a time, and pushes only to pull-request branches; the worst case is a pass finding a branch already current and reporting it as current. So the group goes. If the run still does not start after this, the problem is not in this file — and that will be worth knowing too.
Remove the group that has never let the rebase run start
All checks were successful
CI / Test (Node 18) (pull_request) Successful in 1m37s
CI / Test (Node 20) (pull_request) Successful in 1m29s
CI / Server smoke test (pull_request) Successful in 25s
CI / Docker build (pull_request) Successful in 41s
CI / Test (Node 22) (pull_request) Successful in 1m28s
883f8b5426
Over the whole history of this workflow, the database holds fourteen runs: ten cancelled, four waiting, and not one that ever started. started is epoch 0 on every one of them, including the push-triggered run created when #1083 landed.

They all entered concurrency group 'auto-rebase'. A run that enters a group and never gets a runner blocks every later run in that group - the group drains in order, and the order never advances from the stuck one. cancel-in-progress does not rescue it: it cancels running jobs, not waiting ones, so the waiting runs simply accumulate.

Two rebase passes overlapping is not a correctness problem here. Each pass reads the mergeable flag, rebases one branch at a time, and pushes only to pull-request branches; the worst case is a pass finding a branch already current, which it reports as such.

So the group goes. If this does not make it start, the problem is not in this file.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-08 15:54:29 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1086
No description provided.