You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
β 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.
Activity
don-petry commentedon Oct 22, 2026
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.ymlis needed: the one failure was a real lint error, correctly caught, and it was fixed on the next push.Diagnosis
pull_requestevent for branchfeat/planner-cross-repo-discussion.line-lengtherrors in.github/workflows/initiative-planner.yml(lines 77 and 161: 258 and 312 chars, over the 250 limit).mainpush run passed too. Every run since then has passed.main(.github/workflows/!(*.lock).yml). It passes with warnings only and no errors.Implementation Checklist
Tests to Write
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.
don-petry commentedon Oct 25, 2026
β 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.