[Fleet Monitor] combsmith/google-app-scripts — .github/workflows/coverage.yml #671

Activity

1. don-petry

   added

   health-check

   dev-leadFor dev-lead agent pickupFor dev-lead agent pickup

   fleet-tracker

   on Nov 5, 2026
2. don-petry commented on Nov 5, 2026

   

   don-petry

   on Nov 5, 2026

   CollaboratorAuthor

   More actions

   Dev-Lead Implementation Plan

   Issue: #671 — [Fleet Monitor] combsmith/google-app-scripts — .github/workflows/coverage.yml

   Scope

   Find out why coverage.yml failed. Finding: no code change is needed. Each failure was the workflow correctly catching a broken PR branch, and both were fixed before merge.

   Root-cause analysis (recent failed runs)

   Run	Branch / event	Failing step	Cause	Resolution
   41915491877	fix/npm-audit-glob-minimatch (PR)	npm ci	package.json overrides (glob/minimatch) out of sync with package-lock.json (Missing: glob@10.5.0 from lock file)	Lockfile regenerated; next run on the same PR passed; merged as #667. main push run passed
   41767248874	dev-lead/issue-665-… (PR)	npm test -- --coverage	19 test suites failed to load mid-development	Fixed in later commits on the PR; merged as #666. main push run passed

   • Every push to main in the window passed. Neither failure was flaky or caused by infrastructure.
   • Checked locally at main (52e4ff9): npm ci and npm test -- --coverage both succeed, with 23/23 suites and 1130/1130 tests passing, and node scripts/check-coverage.js passes.

   Implementation Checklist

   • Pull the logs of the failed runs and find the root cause
   • Confirm main is green
   • No workflow or source change. Changing the gate to hide real PR failures would be the wrong fix.

   Tests to Write

   None. Nothing about how the code behaves changes.

   Test Command

   npm test -- --coverage && node scripts/check-coverage.js

   Recommendation

   Close this as expected behaviour. The gate is working. Optional follow-up for Fleet Monitor: count only push/main runs, or don't count PR-branch failures that were fixed before merge, so these alerts stop showing up.
3. don-petry commented on Nov 8, 2026

   

   don-petry

   on Nov 8, 2026

   CollaboratorAuthor

   More actions

   ✅ Auto-resolved by Fleet Monitor. This workflow's failure rate has been below the 10% threshold (or the workflow was removed) since 2026-11-05 (3 days) — the monitor stopped flagging it. Closing. It will reopen automatically if the workflow crosses the threshold again.
4. don-petry

   closed this as completedon Nov 8, 2026