Skip to content

[Fleet Monitor] combsmith/.github-private β€” .github/workflows/ci.ymlΒ #2391

Closed

Description

@don-petry

🟑 WARNING: combsmith/.github-private / .github/workflows/ci.yml

Metric Value
Failure Rate 16.7% (1 / 6 runs)
Status WARNING
p50 Duration 434s
p95 Duration 599s
Successful Runs 5
Cancelled Runs 0

Workflow: .github/workflows/ci.yml

Last updated by Fleet Monitor run on 2026-10-22.
Threshold: failure rate > 10% over the monitored window.

Activity

  1. added
    health-checkAutomated health check report
    dev-leadFor dev-lead agent pickup
    fleet-trackerTracked by the Actions Fleet Monitor
    on Oct 22, 2026
  2. don-petry commented on Oct 22, 2026

    @don-petry
    CollaboratorAuthor

    Dev-Lead Implementation Plan

    Issue: #2391 β€” [Fleet Monitor] combsmith/.github-private β€” .github/workflows/ci.yml

    Scope

    Find out why the run failed. No change to ci.yml is needed: the one failure was a real lint error, correctly caught, and it was fixed on the next push.

    Diagnosis

    • The only failed run in the window is 39684080820. It ran on the pull_request event for branch feat/planner-cross-repo-discussion.
    • The failing job/step was Lint β†’ Lint YAML. yamllint reported line-length errors in .github/workflows/initiative-planner.yml (lines 77 and 161: 258 and 312 chars, over the 250 limit).
    • The next push to that same branch (39687291387) passed. The PR merged, and the main push run passed too. Every run since then has passed.
    • I ran the CI yamllint config locally against current main (.github/workflows/!(*.lock).yml). It passes with warnings only and no errors.

    Implementation Checklist

    • No source change. The failure came from the PR's own code, and CI rejected it as designed. The workflow is not flaky.

    Tests to Write

    • None (no behaviour change).

    Recommendation

    Close this issue as a true positive caught by CI. The 16.7% rate is 1 of 6 runs in a small window, and that one failure is the gate doing its job.

  3. don-petry commented on Oct 25, 2026

    @don-petry
    CollaboratorAuthor

    βœ… Auto-resolved by Fleet Monitor. This workflow's failure rate has been below the 10% threshold (or the workflow was removed) since 2026-10-22 (3 days) β€” the monitor stopped flagging it. Closing. It will reopen automatically if the workflow crosses the threshold again.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    dev-leadFor dev-lead agent pickupfleet-trackerTracked by the Actions Fleet Monitorhealth-checkAutomated health check report

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions