Skip to content

CI gate freshness alert: 1 gate(s) have no recent completed main result #8085

Description

@github-actions

The following post-merge gates have not produced a completed main result within their freshness budget.

This usually means they are starved, not broken — queued behind a merge cadence the runner pool cannot drain (#7856). Check the Actions queue depth before assuming a code failure:

gh api "repos/PerryTS/perry/actions/runs?status=queued&per_page=100" \
  -q '.workflow_runs | length'
gate detail why it matters
security-audit.yml last success result 12.9h ago (budget 12h) Dependency, soak and supply-chain audit called from every main sweep. Reusable-workflow jobs live on test.yml's run, so freshness requires all five nested jobs to complete.

Scheduling rationale and the cost it trades away: docs/src/testing/ci-gate-scheduling.md.

This issue is maintained automatically by gate-freshness.yml. It is updated in place, never duplicated, and closes itself once every gate is fresh again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions