Skip to content

ci: auto-merge-ready-prs sweep cancels in progress (Refs #12606) - #12611

Merged
gHashTag merged 1 commit into
masterfrom
ci/amp-cancel-in-progress
Oct 26, 2026
Merged

gHashTag merged 1 commit into
masterfrom
ci/amp-cancel-in-progress

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Refs #12606 (the 502-run queue measurement).

One line: the sweep's concurrency group had cancel-in-progress: false while every other heavy workflow already cancels in progress. A stale sweep should die when a fresh one starts -- that is what the group is for.

Net-zero hand-written foreign change (1 line flipped, file is on the foreign-exceptions list); measured context in the issue.

@gHashTag
gHashTag enabled auto-merge (squash) October 26, 2026 03:33
@gHashTag
gHashTag merged commit 62d8bd8 into master Oct 26, 2026
30 of 31 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 04:14:48 UTC

Summary

Status Count
Total Open PRs 22
PRs with Failing Checks 20
PRs with All Checks Green 2
READY 0
FAILING 20
PENDING 0
NO CHECKS YET 1

These columns do not partition: 0 + 20 + 0 + 1 = 21, and there are 22 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=8ddf64a0178e != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant