[audit-workflows] π Agentic Workflow Audit β 2026-07-14 (partial; tokens restored, Smoke CI chronic, new crush engine) #45558
Replies: 2 comments
-
|
Smoke tests executed by Copilot. Results forthcoming.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Smoke bot here. Fire good. Run 29372693679 stomp by.
|
Beta Was this translation helpful? Give feedback.
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.
-
π Agentic Workflow Audit β 2026-07-14
Window: partial ~8.5h (12:45β21:14Z) Β· 8-day gap since last audit (07-06). Bridge
logscall hit the 120s cap mid-download, so 105 of ~340 run dirs had full summaries (234 empty). Numbers below are a representative partial slice.Headline: All 19 failures are 0-turn driver failures (agent never produced a turn) β zero agent-logic, missing-tool, missing-data, or MCP failures. Health is on-baseline once the two chronic clusters are excluded.
pi(24/24) andclaude(13/13) were 100%. Avenger β the chronic #1 offender β had 0 runs (paused again).π Trends
Success rate sits at 81.9% (partial slice), below the ~90% healthy band but consistent with prior partial windows once the deterministic
Smoke CIcluster is removed. Failures remain concentrated in the copilot 0-turn family rather than spread across engines.Token reporting is restored: 73.3M this window β the highest since mid-June. The multi-week "token-gap" (06-19β07-13) was a reporting-path artifact:
run.TokenUsage/metrics.TokenUsageare still 0, but real per-run tokens live inagent_usage.json(input+output+cache). Recommend the token chart officially read from that field.π§© Failure taxonomy (all 0-turn)
Full breakdown (19 fails)
1.
copilot-sdk-longrun-0turnβ ~9 fails (DOMINANT, recur count 25)Agent does real work for 9β33 min, then
Execute GitHub Copilot CLIaborts 0-turn:32.8m(new name)20.3m16.6m(new)16.4m15.2m(new)14.6m12.8m(new)10.3m(was chroot-node; now longrun signature)9.4m+ Smoke Copilot Sub Agents6.2m2.
Smoke CI3/3 = 100% (chronic, recur count 7)copilot/claude-sonnet-4.6, 0-turn 4.6β5.0m at Execute Copilot CLI, pushβmain + PR. Deterministic red on main across 7 observed windows (06-30β07-14). Muting/fixing lifts prod-main 83.1%β~86%.3.
Smoke Crush4/4 = 100% β π NEWcrushengine (isolated)anthropic/claude-sonnet-4, 0-turn ~6m, all on branchcopilot/aw-fix-smoke-crush-failureviaworkflow_dispatch. A new engine entered the fleet; failures are confined to an active fix branch β PR-under-review signal, not fleet infra. Flag to branch author; watch for crush reaching prod-main.4.
Daily Cache Strategy Analyzer(codex) β recur count 60-turn 6.2m at Execute Codex CLI (gh-aw binary-not-found for MCP). ~100% fail for ~1 month (06-15β07-14).
5.
Daily Credit Limit Testβ intentional.β Recommendations (evidence-linked)
Smoke CIcopilot-CLI 0-turn on main β single highest-ROI deterministic red; persisted unchanged across the 8-day gap β not self-healing. Add a fast-fail diagnostic dumping why the CLI aborts 0-turn.Execute-CLI0-turn family β ~68% of fleet fails; 4 new affected workflows this window. Instrument stderr/exit-code so 0-turn stops being opaque.Daily Cache Strategy Analyzer(codex) β ~1 month of ~100% fail; burns ~6min/day with zero output. Align the MCP-helper binary lookup path with the build-step placement.agent_usage.jsonβ real per-run tokens are present there (73.3M fleet);run.TokenUsageremains 0. Close the "token-gap" by reading the correct field.crushengine β currently isolated to its fix branch; confirm crush startup before it reaches main/schedule.References: Β§29337445427 Β· Β§29369632935
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