Fix: Execute GitHub Copilot CLI step silently exits early across 3 unrelated workflows
Fix the Copilot CLI execution wrapper — it silently truncates most of its egress traffic and exits early with no visible error, hitting 3 unrelated workflows the same day.
Affected workflows:
Evidence
audit-diff against the nearest successful run of the same Model Resolution Audit workflow (§31998521926) shows:
Traffic volume comparison (failed run vs. known-good run)
| Domain |
Failed run |
Success run |
Change |
api.githubcopilot.com |
6 calls |
20 calls |
-70% |
o205451.ingest.us.sentry.io |
3 calls |
7 calls |
-57% |
otlp-gateway-prod-eu-west-2.grafana.net |
1 call |
5 calls |
-80% |
| GitHub REST core rate-limit consumed |
56 |
609 |
-91% |
No blocked requests, no new/removed domains — ruling out firewall/egress policy as the cause. The failed run simply did far less work before stopping.
In the clearest case (Metrics Collector, 32092825920), the step's own artifact/log post-processing (rpc-messages.jsonl, gateway.md, token-usage.jsonl, AI Credits line) completes cleanly and the job moves on to print_firewall_logs.sh — yet the step is still recorded as failed, with no ##[error], timeout, or auth message anywhere in the captured tail.
Probable root cause
A silent/deferred failure — likely a non-zero exit code or a downstream safe-outputs validation check that fires after the visible Copilot CLI stream ends, since housekeeping still completes normally. Because this hit 3 independent workflows same-day, treat as infra-level (shared Copilot CLI wrapper/harness), not workflow-specific logic.
Proposed remediation
- Instrument the Copilot CLI wrapper to emit an explicit exit-code/error line on termination — a non-zero exit with a clean-looking log is currently indistinguishable from success.
- Audit the safe-outputs post-processing step that runs after the visible Copilot CLI stream ends for a swallowed exception or silent validation failure.
- Prioritize the shared invocation code path over per-workflow logic, given 3 unrelated workflows failed identically the same day.
Success criteria
Execute GitHub Copilot CLI failures surface a specific, non-empty error/exit-code in logs; the three affected workflows either pass or fail with a diagnosable cause, and their traffic-volume profile matches known-good runs.
Parent: #53129
Related to #53129
Generated by 🔍 [aw] Failure Investigator (6h) · agent · 251.3 AIC · ⌖ 6.96 AIC · ⊞ 5.9K · ◷
Fix:
Execute GitHub Copilot CLIstep silently exits early across 3 unrelated workflowsFix the Copilot CLI execution wrapper — it silently truncates most of its egress traffic and exits early with no visible error, hitting 3 unrelated workflows the same day.
Affected workflows:
Evidence
audit-diffagainst the nearest successful run of the same Model Resolution Audit workflow (§31998521926) shows:Traffic volume comparison (failed run vs. known-good run)
api.githubcopilot.como205451.ingest.us.sentry.iootlp-gateway-prod-eu-west-2.grafana.netNo blocked requests, no new/removed domains — ruling out firewall/egress policy as the cause. The failed run simply did far less work before stopping.
In the clearest case (Metrics Collector, 32092825920), the step's own artifact/log post-processing (
rpc-messages.jsonl,gateway.md,token-usage.jsonl, AI Credits line) completes cleanly and the job moves on toprint_firewall_logs.sh— yet the step is still recorded as failed, with no##[error], timeout, or auth message anywhere in the captured tail.Probable root cause
A silent/deferred failure — likely a non-zero exit code or a downstream safe-outputs validation check that fires after the visible Copilot CLI stream ends, since housekeeping still completes normally. Because this hit 3 independent workflows same-day, treat as infra-level (shared Copilot CLI wrapper/harness), not workflow-specific logic.
Proposed remediation
Success criteria
Execute GitHub Copilot CLIfailures surface a specific, non-empty error/exit-code in logs; the three affected workflows either pass or fail with a diagnosable cause, and their traffic-volume profile matches known-good runs.Parent: #53129
Related to #53129