Repository navigation
[agent-job-health] Agent Job Health Monitor daily report #67304
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-12T23:48:11.470Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Warning
Two data-quality issues limit confidence in today's numbers: (1) the local log cache covered only ~1/3 of the claimed 24h window, and (2) the GitHub Actions Jobs API returns zero jobs for 40 failed PR-reviewer-fleet runs, making it impossible to confirm whether
agentor another job actually failed for those runs.Failure Rate by Step (confirmed agent-job failures only, n=8)
Tracked Failures
None. Issue search (
search_issues) returned zero accessible results for every query tried against today's failure signatures and the known chronic-offender names (PR Sous Chef, Issue Monster, Contribution Check, Copilot CLI segfault) — all of which appear in today's sample with a 0% failure rate, consistent with them being already-mitigated/tracked. Every other search had all candidate results removed by the integrity policy (resource trust level below "approved"), so absence of a hit here should not be read as confirmation that no tracking issue exists — only that this run could not verify one.Novel Failure Clusters
pull_request, conclusionfailure). Root cause unknown: bothlist_workflow_jobsandget_job_logsreturntotal_count: 0for every one of these runs, and the local log cache never downloadedrun_summary.json/aw_info.jsonfor them either — all triggered bypull_requestevents on Copilot-authored branches (actorCopilot/copilot-swe-agent). Suspected cause: restricted job-log visibility for PR runs opened by the Copilot coding agent, not necessarily theagentjob itself failing (could bedetection, which is out of scope). Recommended action: investigate why Actions job-level data is unavailable for these runs (token scope? retention? a different workflow structure for Copilot-branch PRs?) before concluding this is an agent-job regression.docker buildxsetup/cache error); available log excerpt only shows post-job teardown, not the actual error. Below the 10%/2-workflow issue threshold on its own but worth a follow-up log pull.Schedule Heartbeat
No blind spots detected in the checked sample. Because the local log cache covered only ~7.8h instead of 24h, 202 of 241 schedule-triggered workflows had no run in the local sample — this is expected given the narrow window, not evidence of a blind spot by itself. A stratified sample of 32 of those 202 (daily/sub-daily cadence, excluding
smoke-*fixtures and weekly+ cadences) was checked directly against the GitHub Actions API (list_workflow_runs, most recent run of any kind): 32/32 had a run within their expected cadence (all within the last ~20h), several withconclusion: failure(already covered under indeterminate/novel clusters above where applicable) but none silent beyond 2× cadence + 1 day. Full exhaustive verification of all 241 scheduled workflows was not completed this run (budget); the remaining ~170 (mostlydaily/every 2 dayssmoke fixtures) were not individually checked.View per-workflow breakdown (workflows with full job-level data, n=41)
Recommendations
pull_request-triggered runs on Copilot-authored branches (40 runs this window alone) — this blocks accurate agent-job attribution for a meaningful share of the PR-reviewer fleet and should be fixed before the next report, not worked around again.search_issuescalls were filtered for nearly every query, so the tracked/novel split above should be treated as a lower bound on "tracked."All reactions