labels-reconcile — a green workflow_dispatch re-run at the same head never clears a red pull_request context, so blocker:ci-red is permanent without a new commit #279
Labels
No labels
attention
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-ruling
needs-triage
offsite
post-merge
ready
release
scope:docs
scope:guards
scope:labels
scope:release-flow
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/ceremony#279
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happened (provider-seeker!240, 2026-10-04)
pull_request, head6a239100): every job green except Coverage floor, task 61655, which failed. Reviewers measured the same command locally at 96.58% ≥ 92%, so it looks like a one-off.workflow_dispatch: run 9098 at the identical head, all 11 jobs green, including Coverage floor (task 61748).6a239100. The builder setstate:needs-human.13:57:04Z) tostate:addressing+blocker:ci-red, and it will keep doing so on every event. The PR can't reachneeds-humanwithout a new commit, and a new commit would make all three approvals stale.Cause
labels-reconcile.shcollapses the rollup newest per context. A dispatch re-run publishes different context names:CI / Coverage floor (>= 92%) (workflow_dispatch)instead of… (pull_request). So the green re-run never replaces the red entry, and the red(pull_request)context stays the newest word for that context forever. It's the same family of problem as #133/#136/#139/#208: a verdict about these exact bytes exists, but the reduction can't see it.Proposal
When collapsing, normalize a context's trailing event suffix: treat
(pull_request),(pull_request_target)and(workflow_dispatch)as the same check, only for entries whose commit SHA equals the PR head. Then the newest verdict about the head wins, whatever event produced it.pull_requestentry with no later green entry of the same job at the same head.Acceptance
X (pull_request)older + greenX (workflow_dispatch)newer, same SHA →SUCCESS. Reversed order →FAILURE.FAILURE.blocker:ci-red.