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
Fix the Daily BYOK Ollama Test warm-up loop first — it has failed every scheduled run for 8 straight days, and nobody is tracking it.
15 failed runs analyzed from this window (2026-08-06 19:42–2026-08-07 01:42 UTC). 5 distinct failure clusters + 8 isolated single-run failures across unrelated workflows. 1 issue reopened (wrongly closed, recurring again within hours), 1 new P0 sub-issue filed, 1 tracked cluster reconfirmed and left untouched, 1 P1 gap folded into this report (create_issue budget: 2/run).
Cluster summary
Sev
Cluster
Runs
Status
P0
Daily BYOK Ollama Test — qwen2.5:0.5b never completes warm-up, 100% failure rate (10/10 runs, 2026-07-27 → 2026-08-07)
8 isolated single-run failures, 8 unrelated workflows, no shared signature
see evidence
No action — monitor only
Evidence
Daily BYOK Ollama Test — 100% failure rate (P0, new sub-issue)
Start Ollama service and Pull small model (397 MB) both succeed in §31134143397.
Warm up model then loops curl -sf .../api/generate 10× at 3s intervals — every single attempt fails, not just the first few — before the step hard-fails with Model 'qwen2.5:0.5b' failed to warm up after 10 attempts.
-sf on curl suppresses the actual HTTP status/body, so the real cause (crash, OOM, request-shape mismatch against the pinned Ollama v0.31.1) is currently invisible in the logs.
Confirmed via agenticworkflows logs --workflow_name "Daily BYOK Ollama Test": 10/10 of the last 10 scheduled runs (back to 2026-07-27) failed identically — this is not a one-off, it is a fully broken daily job.
Full root-cause detail and remediation steps are in the new sub-issue.
Copilot "No model available" — reopening #49022 (P0)
[copilot-sdk-driver] [sdk-driver] error: Execution failed: Error: No model available. Check policy enablement under GitHub Settings > Copilot
[copilot-harness] attempt 4 failed: exitCode=1 failureClass=partial_execution ... retriesRemaining=0
[copilot-harness] all 3 retries exhausted — giving up (exitCode=1)
Same signature confirmed independently in §31131741357 and §31131713448 (8 matching log lines = 4 attempts × 2 emit points each).
This is the exact signature #49022 was filed for, closed not_planned on 2026-08-06 09:31 UTC, and already reopened once before (2026-08-06 07:41 UTC pass) after recurring within hours of an earlier close. It has now recurred a 4th consecutive 6h window. Reopened again this pass with the evidence above — recommend not closing without a code change landing.
Copilot CLI 15-minute step timeout during a legitimate long-running task (P1, untracked, no separate issue this cycle)
agent-stdio.log for §31132973257 shows the agent actively iterating — one bash tool call every 10-20s, methodically reproducing a real sanitizer bypass (protocol-relative-URL userinfo bug) with a dozen node -e regex experiments — right up until:
##[error]The action 'Execute GitHub Copilot CLI' has timed out after 15 minutes.
§31132652013 fails identically. Neither run shows a stuck/hung process — both were doing real, useful work when the clock ran out. This is a task-shape problem, not a bug in the agent: deep security-fix reviews on this workflow can legitimately exceed 15 minutes.
Not filed as a separate sub-issue this cycle (create_issue budget: 1 parent + 1 P0 sub-issue). Recommend either raising PR Code Quality Reviewer's step timeout for its Copilot CLI execution, or splitting long investigative tasks into checkpointed sub-agent calls so partial progress survives a timeout.
Daily Reliability Review — opencode postinstall (tracked, no action)
§31135630380 fails identically to the cluster #50735 already tracks (opencode-ai's postinstall script was not run). No new evidence beyond what #50735 already documents — left untouched.
8 isolated single-run failures — P2, monitor only
Each of the following failed exactly once this window, in 8 different workflows with no shared signature — insufficient signal to justify individual investigation against this cycle's budget. Re-check next window if any recur:
Reopened #49022 — see above. Don't touch the other 6 curated open issues — none show fresh evidence of a fix or staleness this window:#49583 (dispatch_workflow), #49446 (unguarded arithmetic), #50735 (opencode migration — reconfirmed recurring, left open), #50734 (prior parent report, 2026-08-06 — still has open sub-issue work, left open), #50687 (Ambient Context report), #48838 (No-Op Runs), #50819 (Evals Feature report). None closed.
Fix roadmap
P0 — do this first:
Fix Warm up model in daily-byok-ollama-test.md — 100% failure rate, 10/10 runs over 8 days. See sub-issue below.
Fix the
Daily BYOK Ollama Testwarm-up loop first — it has failed every scheduled run for 8 straight days, and nobody is tracking it.15 failed runs analyzed from this window (2026-08-06 19:42–2026-08-07 01:42 UTC). 5 distinct failure clusters + 8 isolated single-run failures across unrelated workflows. 1 issue reopened (wrongly closed, recurring again within hours), 1 new P0 sub-issue filed, 1 tracked cluster reconfirmed and left untouched, 1 P1 gap folded into this report (create_issue budget: 2/run).
Cluster summary
qwen2.5:0.5bnever completes warm-up, 100% failure rate (10/10 runs, 2026-07-27 → 2026-08-07)general-purposesub-agent exhausts all 4 launch attemptsnot_planned2026-08-06 09:31 UTC, refired 3× within 14 hoursExecute GitHub Copilot CLIhits the hard-coded 15-minute step timeout mid a legitimate, long-running security-fix taskopencodepostinstall script never ranEvidence
Daily BYOK Ollama Test — 100% failure rate (P0, new sub-issue)
Start Ollama serviceandPull small model(397 MB) both succeed in §31134143397.Warm up modelthen loopscurl -sf .../api/generate10× at 3s intervals — every single attempt fails, not just the first few — before the step hard-fails withModel 'qwen2.5:0.5b' failed to warm up after 10 attempts.-sfon curl suppresses the actual HTTP status/body, so the real cause (crash, OOM, request-shape mismatch against the pinned Ollama v0.31.1) is currently invisible in the logs.agenticworkflows logs --workflow_name "Daily BYOK Ollama Test": 10/10 of the last 10 scheduled runs (back to 2026-07-27) failed identically — this is not a one-off, it is a fully broken daily job.Copilot "No model available" — reopening #49022 (P0)
agent-stdio.logfor §31134098453:Same signature confirmed independently in §31131741357 and §31131713448 (8 matching log lines = 4 attempts × 2 emit points each).
This is the exact signature #49022 was filed for, closed
not_plannedon 2026-08-06 09:31 UTC, and already reopened once before (2026-08-06 07:41 UTC pass) after recurring within hours of an earlier close. It has now recurred a 4th consecutive 6h window. Reopened again this pass with the evidence above — recommend not closing without a code change landing.Copilot CLI 15-minute step timeout during a legitimate long-running task (P1, untracked, no separate issue this cycle)
agent-stdio.logfor §31132973257 shows the agent actively iterating — onebashtool call every 10-20s, methodically reproducing a real sanitizer bypass (protocol-relative-URL userinfo bug) with a dozennode -eregex experiments — right up until:§31132652013 fails identically. Neither run shows a stuck/hung process — both were doing real, useful work when the clock ran out. This is a task-shape problem, not a bug in the agent: deep security-fix reviews on this workflow can legitimately exceed 15 minutes.
Not filed as a separate sub-issue this cycle (create_issue budget: 1 parent + 1 P0 sub-issue). Recommend either raising
PR Code Quality Reviewer's step timeout for its Copilot CLI execution, or splitting long investigative tasks into checkpointed sub-agent calls so partial progress survives a timeout.Daily Reliability Review — opencode postinstall (tracked, no action)
§31135630380 fails identically to the cluster #50735 already tracks (
opencode-ai's postinstall script was not run). No new evidence beyond what #50735 already documents — left untouched.8 isolated single-run failures — P2, monitor only
Each of the following failed exactly once this window, in 8 different workflows with no shared signature — insufficient signal to justify individual investigation against this cycle's budget. Re-check next window if any recur:
Existing issue correlation
Reopened #49022 — see above. Don't touch the other 6 curated open issues — none show fresh evidence of a fix or staleness this window: #49583 (dispatch_workflow), #49446 (unguarded arithmetic), #50735 (opencode migration — reconfirmed recurring, left open), #50734 (prior parent report, 2026-08-06 — still has open sub-issue work, left open), #50687 (Ambient Context report), #48838 (No-Op Runs), #50819 (Evals Feature report). None closed.
Fix roadmap
P0 — do this first:
Warm up modelindaily-byok-ollama-test.md— 100% failure rate, 10/10 runs over 8 days. See sub-issue below.P1 — next:
3. Raise
PR Code Quality Reviewer's Copilot CLI step timeout (currently 15 min) or checkpoint long investigative sub-tasks so legitimate deep-dive fixes don't get killed mid-work.P2 — monitor only:
Sub-issues created
Warm up modelretry loop indaily-byok-ollama-test.md(P0)References: