[audit-workflows] Agentic Workflow Audit — 2026-06-30 (partial 10.5h): Smoke CI 100%-fail + copilot-CLI 0-turn dominate #42575
Replies: 2 comments
-
|
Smoke bonk. Me touch latest talk. Build live. Many tool rocks fall. Warning Firewall blocked 6 domainsThe following domains were blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "safebrowsingohttpgateway.googleapis.com"
- "www.google.com"See Network Configuration for more information.
|
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been marked as outdated by Agentic Workflow Audit Agent. A newer discussion is available at Discussion #42840. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🔍 Agentic Workflow Audit — 2026-06-30
Window: 2026-06-30 10:44Z → 21:19Z (~10.5h PARTIAL, 2nd half of day) · 171 runs observed
Coverage caveat: the
logstool hit its 60s internal deadline on every call and pagination stalled on a stuck artifact dir at 10:44Z, so the early-morning + overnight hours are unobserved. 06-28 and 06-29 audit-days were also missed/unrecorded. Rates below are for the observed second-half window.TL;DR
📊 Fleet Health (30 days)
Today's 81.3% (partial) sits below the 06-22/24 ~92% baseline, but the drop is concentrated in two copilot push/schedule workflows rather than broad fleet degradation — non-main was 96.5% and
piwas 100%. The pattern echoes the 06-20 (Skillet) and 06-25 (distributed 0-tok) dips where one or two clusters skew the headline.Token reporting has been blind since ~06-19 (the per-run TokenUsage artifact reads 0 fleet-wide), so the cost/token series ends mid-June and no $ figures are available for this window. Restoring token capture is needed before cost trends can resume.
🔴 Key issues
1. NEW — Smoke CI 100% fail on push (HIGH)
copilot/claude-sonnet-4.6, push→main, 4–5 min, Turns=0/Tok=0.pre_activation+activationsucceed; the agent job fails at "Execute GitHub Copilot CLI".2. copilot "Execute GitHub Copilot CLI" 0-turn family — 78% of all fails (HIGH, escalating)
25/32 fleet failures share this exact signature. Two sub-variants:
Continuation of the 06-25 distributed 0-tok agent-startup elevation, now concentrated in the copilot engine (79.5% engine success vs claude 87%, pi 100%). The failing step emits no stderr into artifacts — these 0-turn fails are opaque.
3. Chronic recurrences (unchanged root causes)
NEW (watch): Daily Fact (codex/gpt-5.4) single 0-turn fail at Execute Codex CLI. codex engine ran 40% (2/5) this window.
✅ Healthy signals
pi/gpt-5.40-tok cluster did not recur this window.claude-haiku-4.5(a config change since 06-27) — but did not resolve the err-config fault.🎯 Next actions
rec-smoke-ci-copilot-cli-100pct).rec-copilot-cli-0turn-rootcause).rec-avenger-fix-err-config).Methodology & data quality
aw_info.jsonengine_id(authoritative), not lockfile scanning.run_summary.jsonjob_details[].steps[].References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
awmgmcpgSee Network Configuration for more information.
Beta Was this translation helpful? Give feedback.
All reactions